Triple
T4573821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Cricket World Cup |
E123095
|
entity |
| Predicate | officialBallType |
P3186
|
FINISHED |
| Object | White cricket ball |
—
|
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: White cricket ball | Statement: [1999 Cricket World Cup, officialBallType, White cricket ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialBallType Context triple: [1999 Cricket World Cup, officialBallType, White cricket ball]
-
A.
ballType
chosen
Indicates the specific category or kind of ball associated with an entity.
-
B.
usesOfficialBallSupplier
Indicates that an entity makes use of a designated official supplier for the balls used in its activities or events.
-
C.
usesBallColor
Indicates that an entity performs an action or operates in a way that depends on or involves the color of a ball.
-
D.
typeOfFootball
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
-
E.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.