Triple
T18697015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 Junction 16 |
E457145
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M4 |
—
|
NE NERFINISHED |
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: M4 | Statement: [M4 Junction 16, roadNumber, M4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M4 Context triple: [M4 Junction 16, roadNumber, M4]
-
A.
M4
M4 is a general-purpose macro processing language and preprocessor commonly used in Unix-like build systems and tools such as GNU Autoconf.
-
B.
M4
M4 is one of the lines of the Bucharest Metro rapid transit system, serving several northern and northwestern districts of Romania’s capital.
-
C.
M4
M4 is a New York City bus route that runs through Manhattan, connecting key neighborhoods including Morningside Heights with Midtown and downtown areas.
-
D.
M4
chosen
M4 is a major South African metropolitan route that superseded part of the former National Route 32, serving as an important urban arterial road.
-
E.
M4
M4 is a boat line that operates as part of Geneva’s public transport network, providing passenger service across Lake Geneva.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e8bc408190ab41b3c21003c249 |
completed | April 19, 2026, 11:19 p.m. |
Created at: April 10, 2026, 11:49 a.m.