Triple
T23670166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N9 national road |
E584705
|
entity |
| Predicate | hasRoadNumberBefore |
P127886
|
FINISHED |
| Object | N8 national road |
—
|
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: N8 national road | Statement: [N9 national road, hasRoadNumberBefore, N8 national road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNumberBefore Context triple: [N9 national road, hasRoadNumberBefore, N8 national road]
-
A.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
B.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
C.
hasRoadAbove
Indicates that one road segment is physically located above another, such as on an overpass, bridge, or elevated structure.
-
D.
routeNumberPrecededBy
chosen
Indicates that one route number comes immediately before another route number in an ordered sequence.
-
E.
hasRoadNumberSystem
Indicates that a place or region uses a specific system for assigning numbers to its roads or highways.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40ec52c8190b38a77cc3973d112 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.