Triple
T36629546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E8 |
E904273
|
entity |
| Predicate | appliesToRoadClass |
P165312
|
FINISHED |
| Object | national expressway |
—
|
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: national expressway | Statement: [E8, appliesToRoadClass, national expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRoadClass Context triple: [E8, appliesToRoadClass, national expressway]
-
A.
appliesToRoadType
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
B.
appliesToRoad
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a road.
-
C.
hasRoadClass
chosen
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
-
D.
isRoadPass
Indicates that a particular road or route is currently passable or open for travel.
-
E.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 3, 2026, 4:11 p.m.