Triple
T3596679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Revie |
E76155
|
entity |
| Predicate | shirtNumberInnovation |
P50133
|
FINISHED |
| Object | introduced numbered tactical roles at Leeds United |
—
|
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: introduced numbered tactical roles at Leeds United | Statement: [Don Revie, shirtNumberInnovation, introduced numbered tactical roles at Leeds United]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shirtNumberInnovation Context triple: [Don Revie, shirtNumberInnovation, introduced numbered tactical roles at Leeds United]
-
A.
jerseyNumber
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
shirtColor
Indicates the color attribute associated with a shirt.
-
C.
primaryJerseyDesign
Indicates the main visual design or pattern used on an entity’s primary jersey or uniform.
-
D.
coatCharacteristic
Indicates that one entity has a particular property, feature, or quality that characterizes its outer covering or surface.
-
E.
garmentType
Indicates the specific kind or category of garment associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19b26bc8190b3cc0613a1a98361 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9261a948190b67f6c6ac0dae2e9 |
completed | March 8, 2026, 6 p.m. |
Created at: March 8, 2026, 3:22 p.m.