Triple
T13852832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaya Touré |
E332985
|
entity |
| Predicate | shirtNumberAtManchesterCity |
P2651
|
FINISHED |
| Object | 42 |
—
|
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: 42 | Statement: [Yaya Touré, shirtNumberAtManchesterCity, 42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shirtNumberAtManchesterCity Context triple: [Yaya Touré, shirtNumberAtManchesterCity, 42]
-
A.
shirtNumberType
Indicates the type or category of a shirt number assigned to an entity (for example, a player’s jersey number type).
-
B.
shirtNumberTradition
Indicates a conventional or historically established assignment or significance of a particular shirt number within a team or sport.
-
C.
shirtNumberInnovation
Indicates an association where an entity’s shirt number is linked to a novel or unconventional change, method, or feature related to numbering.
-
D.
roleInManchesterCity
Indicates that an entity holds or has held a specific role or position within Manchester City Football Club.
-
E.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.