Triple
T27581703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Watson |
E699600
|
entity |
| Predicate | dateOfJeopardyMatch |
P29412
|
FINISHED |
| Object | 2011-02 |
—
|
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: 2011-02 | Statement: [IBM Watson, dateOfJeopardyMatch, 2011-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfJeopardyMatch Context triple: [IBM Watson, dateOfJeopardyMatch, 2011-02]
-
A.
recordGameDate
Indicates that an entity logs or stores the date on which a particular game took place or is scheduled.
-
B.
typicalGameDate
Indicates the usual or standard calendar date on which a particular game is played or scheduled to occur.
-
C.
game1Date
Indicates the calendar date on which the first game or match in a series takes place.
-
D.
eventDateJudged
Indicates that a specific date has been evaluated or determined in relation to an event (e.g., as its official or relevant date).
-
E.
playedOnDate
chosen
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 2:03 p.m.