Triple
T32001495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotter'N Hell Hundred |
E817140
|
entity |
| Predicate | hasEventComponent |
P6285
|
FINISHED |
| Object | road cycling ride |
—
|
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: road cycling ride | Statement: [Hotter'N Hell Hundred, hasEventComponent, road cycling ride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventComponent Context triple: [Hotter'N Hell Hundred, hasEventComponent, road cycling ride]
-
A.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
B.
hasSubEvent
chosen
Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
-
C.
hasEventSpace
Indicates that an entity provides or includes a designated space intended for hosting events.
-
D.
hasEventHandler
Indicates that one entity is responsible for handling or responding to events triggered by another entity.
-
E.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3fbfe4c8190bc1591394bc8ebb4 |
completed | May 3, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:14 a.m.