Triple
T23280791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandrabhaga |
E588854
|
entity |
| Predicate | localNameOf |
P24351
|
FINISHED |
| Object | Bhima 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: Bhima River | Statement: [Chandrabhaga, localNameOf, Bhima River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localNameOf Context triple: [Chandrabhaga, localNameOf, Bhima River]
-
A.
localNameDefinition
Indicates that an entity’s locally scoped name is defined or specified within a particular context or namespace.
-
B.
hasLocalNameFor
chosen
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
-
C.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
D.
modernLocalName
Indicates the current, locally used name or designation for an entity, as recognized in the present time.
-
E.
notableLocalName
Indicates that an entity is known by a notable or commonly used local name within a specific region or community.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:56 p.m.