Triple
T19416555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belisha beacon |
E485730
|
entity |
| Predicate | trafficSystemRole |
P25845
|
FINISHED |
| Object | uncontrolled crossing marker |
—
|
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: uncontrolled crossing marker | Statement: [Belisha beacon, trafficSystemRole, uncontrolled crossing marker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficSystemRole Context triple: [Belisha beacon, trafficSystemRole, uncontrolled crossing marker]
-
A.
roadSystemRole
chosen
Indicates the specific functional role or responsibility an entity has within a road or transportation network system.
-
B.
roadOperator
Indicates that one entity is responsible for operating, managing, or maintaining a particular road or road network.
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
E.
railwayTrafficRole
Indicates the specific function or responsibility an entity has within the operation, management, or control of railway traffic.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af9c8fc81909860de10b6720207 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.