Triple
T34615744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Midtjylland |
E888858
|
entity |
| Predicate | usesDataAnalytics |
P38333
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: yes | Statement: [FC Midtjylland, usesDataAnalytics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDataAnalytics Context triple: [FC Midtjylland, usesDataAnalytics, yes]
-
A.
usedDataAnalytics
chosen
Indicates that an entity applied data analytics techniques or insights in performing an action or making a decision related to another entity.
-
B.
usesDataIn
Indicates that one entity relies on, accesses, or incorporates data from another entity in performing its function or operation.
-
C.
usesDataProcessing
Indicates that one entity applies data processing techniques or operations to data associated with another entity.
-
D.
hasAnalyticUse
Indicates that something is used for analysis, examination, or systematic study of another thing or situation.
-
E.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.