Triple
T7616004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aller Valley |
E172361
|
entity |
| Predicate | transportCorridorAlong |
P70574
|
FINISHED |
| Object | Aller River |
—
|
NE NERFINISHED |
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: Aller River | Statement: [Aller Valley, transportCorridorAlong, Aller River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportCorridorAlong Context triple: [Aller Valley, transportCorridorAlong, Aller River]
-
A.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
B.
partOfTransportCorridorTo
Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
-
C.
formsTransportCorridorBetween
chosen
Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
-
D.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa4569c88190b2968403a24e7882 |
completed | March 27, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.