Triple
T12257393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleg Salenko |
E292135
|
entity |
| Predicate | shirtNumberAt1994WorldCup |
P2651
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Oleg Salenko, shirtNumberAt1994WorldCup, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shirtNumberAt1994WorldCup Context triple: [Oleg Salenko, shirtNumberAt1994WorldCup, 9]
-
A.
shirtNumberTradition
Indicates a conventional or historically established assignment or significance of a particular shirt number within a team or sport.
-
B.
roleIn1999WorldCup
Indicates the specific capacity or position an entity held in relation to the 1999 World Cup event.
-
C.
shirtNumberType
Indicates the type or category of a shirt number assigned to an entity (for example, a player’s jersey number type).
-
D.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
E.
shirtNumberInnovation
Indicates an association where an entity’s shirt number is linked to a novel or unconventional change, method, or feature related to numbering.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.