Triple
T37040435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iditarod Trail Sled Dog Race 2004 |
E916764
|
entity |
| Predicate | heldInTimeInterval |
P54578
|
FINISHED |
| Object | March 2004 |
—
|
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: March 2004 | Statement: [Iditarod Trail Sled Dog Race 2004, heldInTimeInterval, March 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInTimeInterval Context triple: [Iditarod Trail Sled Dog Race 2004, heldInTimeInterval, March 2004]
-
A.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
-
B.
heldByUntil
Indicates that an entity maintains possession or control of something up to, but not necessarily beyond, a specified time or condition.
-
C.
heldWhen
chosen
Indicates that a particular state, condition, or relationship was true during a specified time or under certain temporal circumstances.
-
D.
recordHeldDuration
Indicates the length of time for which a particular record, title, or achievement was continuously held.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.