Triple
T35743404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giridih Lok Sabha constituency |
E1033103
|
entity |
| Predicate | cameUnderState |
P160247
|
FINISHED |
| Object | Jharkhand |
—
|
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: Jharkhand | Statement: [Giridih Lok Sabha constituency, cameUnderState, Jharkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameUnderState Context triple: [Giridih Lok Sabha constituency, cameUnderState, Jharkhand]
-
A.
becameStateOf
Indicates that an entity transitioned into and assumed the status, condition, or role defined by a particular state.
-
B.
cameUnderSector
Indicates that one entity became subject to the authority, control, or jurisdiction of a particular sector or administrative division.
-
C.
emergedUnder
Indicates that one entity came into existence, prominence, or recognition during the authority, period, or influence of another entity.
-
D.
cededUnder
Indicates that control, ownership, or rights over something are transferred from one party to another under specified terms or conditions.
-
E.
becamePartOfState
chosen
Indicates that an entity transitioned from a different status or jurisdiction to become incorporated into a particular 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.