Triple
T11444265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baitarani River (upper catchments) |
E271223
|
entity |
| Predicate | flowDirectionFromRegion |
P8846
|
FINISHED |
| Object | eastward |
—
|
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: eastward | Statement: [Baitarani River (upper catchments), flowDirectionFromRegion, eastward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowDirectionFromRegion Context triple: [Baitarani River (upper catchments), flowDirectionFromRegion, eastward]
-
A.
flowsTowardRegion
Indicates that something (such as a fluid, substance, or traffic) moves in the direction of and approaches a specified region.
-
B.
drainageDirection
chosen
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
pilgrimFlowDirection
Indicates the direction in which pilgrims move or travel along a route, path, or within a pilgrimage site.
-
D.
flowsThroughRegionType
Indicates that something such as a fluid, current, or pathway passes through and traverses a specified type of region.
-
E.
dataFlowDirection
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088a66f48190b2b4a56cd62097cf |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.