Triple
T4611847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beas |
E100575
|
entity |
| Predicate | riverineFeature |
P14635
|
FINISHED |
| Object | floodplain of Beas River |
—
|
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: floodplain of Beas River | Statement: [Beas, riverineFeature, floodplain of Beas River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverineFeature Context triple: [Beas, riverineFeature, floodplain of Beas River]
-
A.
riverFeatureType
chosen
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
B.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
C.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
D.
reservoirRiver
Indicates that a reservoir is supplied or drained by, and thus hydrologically connected to, a particular river.
-
E.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59bffbf08190b13ef0810e6f9d19 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.