Triple
T807769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elm Street (Dallas) |
E17475
|
entity |
| Predicate | hasRoadSurface |
P422
|
FINISHED |
| Object | asphalt |
—
|
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: asphalt | Statement: [Elm Street (Dallas), hasRoadSurface, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadSurface Context triple: [Elm Street (Dallas), hasRoadSurface, asphalt]
-
A.
roadwayCarries
Indicates that a roadway serves as a route that supports or conveys a particular transportation facility, traffic flow, or designated use.
-
B.
runwaySurface
chosen
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
C.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.