Triple
T26227623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sravasti |
E655938
|
entity |
| Predicate | stateDistrict |
P84299
|
FINISHED |
| Object | Shravasti district |
—
|
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: Shravasti district | Statement: [Sravasti, stateDistrict, Shravasti district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateDistrict Context triple: [Sravasti, stateDistrict, Shravasti district]
-
A.
governorateOrDistrict
Indicates that one administrative region is a governorate or district that encompasses, governs, or is otherwise the primary subnational division for another area or locality.
-
B.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
C.
stateUnit
Indicates a relationship where one entity is a constituent administrative or organizational unit within a larger state or state-like structure.
-
D.
stateSeat
Indicates that one entity serves as the official seat or capital location of a state-level governmental body for the other entity.
-
E.
hasStateOrDistrict
chosen
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 26, 2026, 8:58 p.m.