Triple
T4230274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keith Yandle |
E94562
|
entity |
| Predicate | ironmanStreakStartDate |
P54809
|
FINISHED |
| Object | 2009-03-26 |
—
|
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: 2009-03-26 | Statement: [Keith Yandle, ironmanStreakStartDate, 2009-03-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ironmanStreakStartDate Context triple: [Keith Yandle, ironmanStreakStartDate, 2009-03-26]
-
A.
hittingStreakStartDate
Indicates the date on which a continuous sequence of successful hits (a hitting streak) begins.
-
B.
hittingStreakEndDate
Indicates the date on which a continuous sequence of successful hits or performances comes to an end.
-
C.
notableStreakMatch
Indicates that a match is part of a significant or noteworthy streak (such as consecutive wins, losses, or performances) associated with an entity.
-
D.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e62e3c881909ffb9269ba9018b9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.