Triple
T27409255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pranhita River |
E692095
|
entity |
| Predicate | mouthLocatedInState |
P101073
|
FINISHED |
| Object | Telangana |
—
|
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: Telangana | Statement: [Pranhita River, mouthLocatedInState, Telangana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthLocatedInState Context triple: [Pranhita River, mouthLocatedInState, Telangana]
-
A.
mouthLocatedInAdministrativeEntity
Indicates that the place where a river ends (its mouth) is situated within a specific administrative region or jurisdiction.
-
B.
mouthOf
Indicates the location where one entity (typically a river or similar feature) empties into or opens out into another, larger body or feature.
-
C.
mouthState
Indicates the current condition or configuration of an entity’s mouth, such as whether it is open, closed, or in another specific state.
-
D.
mouthCountrySubdivision
chosen
Indicates the country subdivision (such as a state or province) in which the mouth or endpoint of a geographic feature (typically a river) is located.
-
E.
cityAtMouth
Indicates that a city is located at or very near the mouth (outlet) of a river.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd99324819099a95e2729e966e9 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:31 p.m.