Triple
T30441049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 Junction 19 |
E774443
|
entity |
| Predicate | previousJunctionOnM1 |
P195681
|
FINISHED |
| Object | M1 Junction 18 |
—
|
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: M1 Junction 18 | Statement: [M1 Junction 19, previousJunctionOnM1, M1 Junction 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousJunctionOnM1 Context triple: [M1 Junction 19, previousJunctionOnM1, M1 Junction 18]
-
A.
nextJunctionOnM1
Indicates that one junction is the immediate subsequent junction along the M1 route from another junction.
-
B.
previousStationOnLine1
Indicates that one station is the immediately preceding station to another station along transit line 1.
-
C.
previousStationOnLineA
Indicates that one station is immediately before another station along line A in the route order.
-
D.
precedingStation
Indicates that one station is located immediately before another station in a route or sequence.
-
E.
precedingStationTowards
Indicates that one station is immediately before another station along a specified direction or route toward a given destination.
- F. None of above. chosen
Provenance (4 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: April 29, 2026, 8:08 p.m.