Triple
T18133752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-1 Rail line |
E434081
|
entity |
| Predicate | safetySystem |
P840
|
FINISHED |
| Object | traffic-signal priority at some intersections |
—
|
LITERAL FINISHED |
How this triple was built (1 step)
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: traffic-signal priority at some intersections | Statement: [M-1 Rail line, safetySystem, traffic-signal priority at some intersections]
Provenance (2 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de04321c81909c0b9d47757720fd |
completed | April 19, 2026, 1:52 p.m. |
Created at: April 10, 2026, 10:29 a.m.