Triple
T10857407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simister Island interchange |
E256303
|
entity |
| Predicate | junctionNumberOnM60 |
P44763
|
FINISHED |
| Object | 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: 18 | Statement: [Simister Island interchange, junctionNumberOnM60, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: junctionNumberOnM60 Context triple: [Simister Island interchange, junctionNumberOnM60, 18]
-
A.
hasJunctionNumberOnM60
chosen
Indicates that an entity has a specific junction number assigned on the M60 motorway.
-
B.
hasConnectingRoadNumber
Indicates that there exists a road connection between two locations or road segments identified by a specific road number.
-
C.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or system.
-
D.
hasJunctionNumber
Indicates that a road, route, or similar pathway is assigned a specific junction or exit number.
-
E.
hasJunctionNumbering
Indicates that a road or route is assigned a specific numbering system for its junctions or intersections.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.