Triple
T7547289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marylebone Road |
E178437
|
entity |
| Predicate | hasPedestrianCrossings |
P23122
|
FINISHED |
| Object | multiple signal-controlled crossings |
—
|
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: multiple signal-controlled crossings | Statement: [Marylebone Road, hasPedestrianCrossings, multiple signal-controlled crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianCrossings Context triple: [Marylebone Road, hasPedestrianCrossings, multiple signal-controlled crossings]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
hasPedestrianOverpass
Indicates that there exists a pedestrian overpass connecting or spanning parts of the referenced location or infrastructure.
-
C.
pedestriansCanCross
chosen
Indicates that pedestrians are permitted or able to cross from one side of a specified location or path to the other.
-
D.
hasPedestrianPhase
Indicates that a traffic signal includes a dedicated phase during which pedestrians are allowed to cross.
-
E.
hasMajorRailCrossing
Indicates that there is a significant railway crossing (such as a major rail line intersecting a road or another transport route) at or associated with the referenced location or entity.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f89a7b2c8190b2ca57edbb4f0390 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.