Triple
T32959286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oostelijke Ourthe |
E843187
|
entity |
| Predicate | heeftStroomrichting |
P75396
|
FINISHED |
| Object | noordwaarts (globaal) |
—
|
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: noordwaarts (globaal) | Statement: [Oostelijke Ourthe, heeftStroomrichting, noordwaarts (globaal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heeftStroomrichting Context triple: [Oostelijke Ourthe, heeftStroomrichting, noordwaarts (globaal)]
-
A.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
B.
hasDirectionOfFlow
Indicates that something moves or is transmitted from one entity or location toward another along a specific path or orientation.
-
C.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
D.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
-
E.
waterwayDirection
chosen
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17799888190a57b3e104bf5da6a |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.