Triple
T38007682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachad village |
E948276
|
entity |
| Predicate | locatedInStateOfIndia |
P202251
|
FINISHED |
| Object | Maharashtra |
E19223
|
NE FINISHED |
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: Maharashtra | Statement: [Pachad village, locatedInStateOfIndia, Maharashtra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInStateOfIndia Context triple: [Pachad village, locatedInStateOfIndia, Maharashtra]
-
A.
locatedInIndianState
chosen
Indicates that one entity is geographically situated within the boundaries of a specific Indian state.
-
B.
partlyLocatedInIndianState
Indicates that an entity is geographically or administratively situated such that only part of it lies within the boundaries of a specified Indian state.
-
C.
locatedInUnionTerritory
Indicates that an entity is geographically situated within a specified union territory.
-
D.
isPartOfIndianState
Indicates that one entity is a constituent part or subdivision of an Indian state.
-
E.
includesIndianStateOrTerritory
Indicates that one entity encompasses, contains, or covers the area of an Indian state or union territory.
- F. None of above.
Provenance (4 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d27f00481908dae3b0a4a1436cf |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.