Triple
T19953685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoddesden |
E479626
|
entity |
| Predicate | roadAccessArea |
P137979
|
FINISHED |
| Object | Hampshire road network |
—
|
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: Hampshire road network | Statement: [Shoddesden, roadAccessArea, Hampshire road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessArea Context triple: [Shoddesden, roadAccessArea, Hampshire road network]
-
A.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
B.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
C.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
D.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
E.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65aee23488190bd92c1593fbc241c |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.