Triple
T32001478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotter'N Hell Hundred |
E817140
|
entity |
| Predicate | hasDistanceOption |
P196666
|
FINISHED |
| Object | 100 miles |
—
|
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: 100 miles | Statement: [Hotter'N Hell Hundred, hasDistanceOption, 100 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistanceOption Context triple: [Hotter'N Hell Hundred, hasDistanceOption, 100 miles]
-
A.
hasDistanceElement
Indicates that one entity includes or is associated with a component that specifies a distance value or measurement.
-
B.
hasDistanceCategory
Indicates that one entity is associated with a qualitative or categorical classification of its distance relative to another entity or reference point.
-
C.
hasDistanceUnit
Indicates that a specified unit of measurement is used to express a distance value in the relationship.
-
D.
hasMultipleDistances
Indicates that a relationship or connection involves more than one distinct distance or separation value between the related entities.
-
E.
hasDistanceReference
Indicates that a distance value is specified relative to a particular reference point, scale, or standard.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 1, 2026, 12:14 a.m.