Triple
T15175785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolts Way |
E362604
|
entity |
| Predicate | roadNumberType |
P117006
|
FINISHED |
| Object | tourist drive designation |
—
|
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: tourist drive designation | Statement: [Thunderbolts Way, roadNumberType, tourist drive designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadNumberType Context triple: [Thunderbolts Way, roadNumberType, tourist drive designation]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
roadNumberPrefix
Indicates that one entity is a prefix portion of the road number or designation used by the other entity.
-
C.
roadNumberingZone
Indicates the designated numbering zone or area within which a particular road’s identification or route number is assigned.
-
D.
routeNumber
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
E.
isNumberedHighway
Indicates that a roadway is officially designated and signed as a numbered highway within a road network.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0066236d481909e8ac47f496861ad |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.