Triple
T12375328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metropolitan Route 482 |
E295107
|
entity |
| Predicate | isUrbanExpressway |
P52196
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Tokyo Metropolitan Route 482, isUrbanExpressway, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanExpressway Context triple: [Tokyo Metropolitan Route 482, isUrbanExpressway, no]
-
A.
isUrbanFreeway
Indicates that a roadway segment functions as a high-capacity, limited-access freeway located within an urban area.
-
B.
isUrbanRoute
chosen
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
C.
isFreeway
Indicates that a given road segment functions as a freeway, typically designed for high-speed, limited-access vehicular traffic.
-
D.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
E.
isRuralHighway
Indicates that a given highway is classified as being located in or primarily serving a rural area.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.