Triple
T22942902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackwater Valley Path |
E569781
|
entity |
| Predicate | isLinearRoute |
P144676
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Blackwater Valley Path, isLinearRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinearRoute Context triple: [Blackwater Valley Path, isLinearRoute, true]
-
A.
isLinear
Indicates that a relationship, function, or structure preserves linearity, typically meaning it satisfies additivity and homogeneity (or forms a straight-line dependence between variables).
-
B.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
C.
isPublicTransportRoute
Indicates that a given route is designated and operated as part of a public transportation system available for general use.
-
D.
isRadialRouteOf
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
E.
isNonBranchingLine
chosen
Indicates that a line continues without any splits, branches, or divergences along its length.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819a509481908a3662ef80f757c7 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.