Triple
T21304994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue de Breteuil |
E525171
|
entity |
| Predicate | hasSideLanes |
P2128
|
FINISHED |
| Object | two carriageways |
—
|
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: two carriageways | Statement: [Avenue de Breteuil, hasSideLanes, two carriageways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideLanes Context triple: [Avenue de Breteuil, hasSideLanes, two carriageways]
-
A.
hasLanes
chosen
Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
-
B.
hasDedicatedLanes
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
C.
hasTrackLanes
Indicates that an entity (such as a road or track) includes one or more designated lanes for vehicle or train movement.
-
D.
hasCarpoolLanes
Indicates that a road, route, or transportation facility includes designated carpool (high-occupancy vehicle) lanes available for use.
-
E.
hasEmergencyLane
Indicates that a road, route, or similar thoroughfare includes a designated emergency lane for use by emergency or breakdown situations.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa341908190963c4368708860b8 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.