Triple
T26178893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neelam River |
E654616
|
entity |
| Predicate | hasNameInIndia |
P174331
|
FINISHED |
| Object | Kishanganga River |
—
|
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: Kishanganga River | Statement: [Neelam River, hasNameInIndia, Kishanganga River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInIndia Context triple: [Neelam River, hasNameInIndia, Kishanganga River]
-
A.
nameInHindi
Indicates that one entity is the Hindi-language name or label corresponding to another entity.
-
B.
hasNameInPunjabi
Indicates that an entity is associated with a specific name expressed in the Punjabi language.
-
C.
hasNameInGujarati
Indicates that an entity is associated with a specific name expressed in the Gujarati language.
-
D.
downstreamNameInIndia
Indicates that the referenced entity is known by this specific name in the downstream (later-stage or consumer-facing) context within India.
-
E.
nameInSanskrit
Indicates that one entity is the name or designation of another entity when expressed in the Sanskrit language.
- F. None of above. chosen
Provenance (4 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 26, 2026, 8:39 p.m.