Triple
T12846019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-1 Motorway |
E307176
|
entity |
| Predicate | hasControlledEntryExit |
P5650
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [M-1 Motorway, hasControlledEntryExit, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlledEntryExit Context triple: [M-1 Motorway, hasControlledEntryExit, yes]
-
A.
hasEntranceControl
chosen
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
D.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
E.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.