Triple
T36758517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janakpurdham |
E908122
|
entity |
| Predicate | borderStateAcrossIndia |
P85007
|
FINISHED |
| Object | Bihar |
—
|
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: Bihar | Statement: [Janakpurdham, borderStateAcrossIndia, Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStateAcrossIndia Context triple: [Janakpurdham, borderStateAcrossIndia, Bihar]
-
A.
borderingIndianStates
chosen
Indicates that one or more Indian states share a common land or maritime boundary with a given geographic or political entity.
-
B.
stateInIndia
Indicates that a given state is located within the country of India.
-
C.
borderingUnionTerritory
Indicates that one entity shares a land or maritime boundary with a specified Union Territory.
-
D.
borderSecurityAgencyIndia
Indicates a relationship where an Indian agency is responsible for managing or enforcing border security.
-
E.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:12 p.m.