Triple
T24162212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R9 |
E598871
|
entity |
| Predicate | wornShirtNumber |
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: [R9, wornShirtNumber, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornShirtNumber Context triple: [R9, wornShirtNumber, 9]
-
A.
jerseyNumber
chosen
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
B.
hasShirtNumberRole
Indicates that an entity holds a specific shirt number assignment or role, typically within a team or roster context.
-
C.
jerseyNumberWornAtGame
Indicates the specific jersey number an entity wore during a particular game or match.
-
D.
wearsJerseyFor
Indicates that one entity wears a jersey representing, belonging to, or in support of another entity (such as a team, organization, or individual).
-
E.
hasDressNumber
Indicates that an entity (typically a player or performer) is associated with a specific dress or jersey number.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.