Triple
T36365165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saran region |
E895601
|
entity |
| Predicate | hasRiverinePlain |
P94450
|
FINISHED |
| Object | Gangetic plain |
—
|
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: Gangetic plain | Statement: [Saran region, hasRiverinePlain, Gangetic plain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverinePlain Context triple: [Saran region, hasRiverinePlain, Gangetic plain]
-
A.
locatedInRiverPlain
chosen
Indicates that something is situated within the flat, low-lying area formed by a river’s floodplain.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
-
D.
hasCoastalPlain
Indicates that an entity possesses or includes a coastal plain as part of its geographic area.
-
E.
hasRiparianZone
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:10 p.m.