Triple
T679353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago River |
E13146
|
entity |
| Predicate | flowDirectionBeforeReversal |
P8846
|
FINISHED |
| Object | from west to east into Lake Michigan |
—
|
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: from west to east into Lake Michigan | Statement: [Chicago River, flowDirectionBeforeReversal, from west to east into Lake Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowDirectionBeforeReversal Context triple: [Chicago River, flowDirectionBeforeReversal, from west to east into Lake Michigan]
-
A.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
C.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
D.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
E.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04f4efc819082767a7517fa760a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.