Triple
T30788266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R102 road |
E784013
|
entity |
| Predicate | usesFormerSectionsOf |
P102403
|
FINISHED |
| Object | former N2 alignment |
—
|
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: former N2 alignment | Statement: [R102 road, usesFormerSectionsOf, former N2 alignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFormerSectionsOf Context triple: [R102 road, usesFormerSectionsOf, former N2 alignment]
-
A.
isOlderSectionOf
Indicates that one section predates another in time or origin, making it the older of the two.
-
B.
usesFormerRouteOf
chosen
Indicates that one route, service, or pathway currently follows all or part of the alignment or path that was previously used by another route.
-
C.
followsSectionOf
Indicates that one section directly comes after or succeeds another section in an ordered structure.
-
D.
hasBackwardsSection
Indicates that an entity contains a segment or portion that is oriented, ordered, or directed in the reverse of the primary or expected direction.
-
E.
previouslyCoveredBy
Indicates that something was earlier protected, enclosed, or overlaid by another object or material, but is no longer in that state.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:41 p.m.