Triple
T6499697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M96 motorway |
E148852
|
entity |
| Predicate | isPublicThroughRoute |
P30373
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [M96 motorway, isPublicThroughRoute, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicThroughRoute Context triple: [M96 motorway, isPublicThroughRoute, no]
-
A.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
B.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
C.
isPubliclyAccessible
chosen
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
D.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
E.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:42 p.m.