Triple
T26185294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhopal district |
E654810
|
entity |
| Predicate | hasMajorRiverOrLake |
P123528
|
FINISHED |
| Object | Upper Lake |
—
|
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: Upper Lake | Statement: [Bhopal district, hasMajorRiverOrLake, Upper Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRiverOrLake Context triple: [Bhopal district, hasMajorRiverOrLake, Upper Lake]
-
A.
hasMajorLake
Indicates that a geographic region or area contains at least one significant lake within its boundaries.
-
B.
hasMajorLakeAtSource
Indicates that the source of a river or stream is located in, or directly associated with, a major lake.
-
C.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasLakes
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 26, 2026, 8:42 p.m.