Triple
T5084770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Park Drive loop road |
E114608
|
entity |
| Predicate | isMainRoad |
P61203
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Park Drive loop road, isMainRoad, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainRoad Context triple: [Park Drive loop road, isMainRoad, true]
-
A.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
C.
isPublicRoad
Indicates that a given road is officially designated and accessible for use by the general public.
-
D.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75192d188190a7631bce5faf7de3 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73b2c2808190b777e2c2a8a45d3f |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:40 p.m.