Triple
T4191640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleven Cities Tour |
E89049
|
entity |
| Predicate | heldWhen |
P54578
|
FINISHED |
| Object | sufficient natural ice conditions |
—
|
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: sufficient natural ice conditions | Statement: [Eleven Cities Tour, heldWhen, sufficient natural ice conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldWhen Context triple: [Eleven Cities Tour, heldWhen, sufficient natural ice conditions]
-
A.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
B.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
C.
heldEvery
Indicates that an entity consistently possessed or maintained control of another entity throughout every instance or period within a specified range.
-
D.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
-
E.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af04af4e44819098a9d7f91e65adf2 |
completed | March 9, 2026, 5:34 p.m. |
Created at: March 9, 2026, 3:46 p.m.