Triple
T585981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leeds United F.C. |
E15157
|
entity |
| Predicate | majorHonour |
P4123
|
FINISHED |
| Object | English top-flight league title |
—
|
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: English top-flight league title | Statement: [Leeds United F.C., majorHonour, English top-flight league title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorHonour Context triple: [Leeds United F.C., majorHonour, English top-flight league title]
-
A.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
B.
honourType
chosen
Indicates the specific category or classification of an honour or award associated with an entity.
-
C.
honour
Indicates showing respect, admiration, or recognition toward someone or something, often through actions, words, or ceremonial acknowledgment.
-
D.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
-
E.
confersKnighthood
Indicates that one entity formally grants the status or title of knighthood to another entity.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9a46388190a094b9ebf8dec397 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494ca68448190a516b9c3525d8916 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.