Triple
T19019177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Najafgarh Assembly constituency |
E465437
|
entity |
| Predicate | isPublicBodyTerritory |
P133572
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Najafgarh Assembly constituency, isPublicBodyTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicBodyTerritory Context triple: [Najafgarh Assembly constituency, isPublicBodyTerritory, yes]
-
A.
hasBodyRegion
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
B.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
-
C.
isPublicBodyOf
Indicates that an entity functions as the official public body or authority associated with, responsible for, or governing another entity.
-
D.
isInBody
Indicates that one entity is physically contained within or located inside the body of another entity.
-
E.
protectsBodyPart
Indicates that one entity serves to shield, guard, or defend a specific body part from harm or damage.
- F. None of above. chosen
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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6ddc9608190a1daec9ddcc79a7a |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.