Triple
T29323251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janakpuri Assembly constituency |
E743569
|
entity |
| Predicate | createdForBody |
P7551
|
FINISHED |
| Object | Delhi Legislative Assembly |
—
|
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: Delhi Legislative Assembly | Statement: [Janakpuri Assembly constituency, createdForBody, Delhi Legislative Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdForBody Context triple: [Janakpuri Assembly constituency, createdForBody, Delhi Legislative Assembly]
-
A.
createdBody
Indicates that one entity brought another entity into existence or produced it as a result of its actions.
-
B.
createdFor
chosen
Indicates that one entity was made, produced, or designed specifically to serve, benefit, or be used by another entity.
-
C.
createdOrAffectedBody
Indicates that an entity either brought a body into existence or caused a change or impact to that body.
-
D.
createdForMedium
Indicates that something was created specifically for use, display, or performance in a particular medium or format.
-
E.
createdForWorkBy
Indicates that something was created specifically for use in work or professional activities by a particular agent or person.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 28, 2026, 1:24 p.m.