Triple
T35743262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giridih district |
E1033098
|
entity |
| Predicate | wasTransferredToState |
P17241
|
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 district, wasTransferredToState, Jharkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTransferredToState Context triple: [Giridih district, wasTransferredToState, Jharkhand]
-
A.
flagStateAfterTransfer
Indicates the resulting status or condition of a flag after a transfer action has been completed.
-
B.
emigratedToState
Indicates that a person or group moved from their previous country or region to take up residence in a specified state.
-
C.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
D.
hasTransfer
chosen
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
E.
transferredAdministrationTo
Indicates that control or management authority over something was handed over from one party to another.
- 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.