Triple
T26453653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakradharpur |
E665422
|
entity |
| Predicate | divisionCoversStates |
P110852
|
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: [Chakradharpur, divisionCoversStates, Jharkhand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionCoversStates Context triple: [Chakradharpur, divisionCoversStates, Jharkhand]
-
A.
dividedStatesInto
Indicates that one entity partitioned another entity into multiple distinct states or regions.
-
B.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
C.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
D.
geographicDivision
chosen
Indicates that one place is an administrative or territorial subdivision of another place.
-
E.
federalDivision
Indicates that one entity is a federal-level administrative or political subdivision (such as a state, province, or territory) within the jurisdiction of another entity.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61266f0e88190aea95f89ba2bef5c |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 12:07 a.m.