Triple
T16235419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haryana Legislative Council |
E394095
|
entity |
| Predicate | creationRequires |
P100
|
FINISHED |
| Object | resolution by Haryana Legislative Assembly |
—
|
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: resolution by Haryana Legislative Assembly | Statement: [Haryana Legislative Council, creationRequires, resolution by Haryana Legislative Assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationRequires Context triple: [Haryana Legislative Council, creationRequires, resolution by Haryana Legislative Assembly]
-
A.
creationType
Indicates the manner or process by which something was brought into existence or produced.
-
B.
crea
Indicates that one entity creates, produces, or brings into existence another entity.
-
C.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of another entity.
-
D.
productionRequirement
Indicates a condition or resource that must be fulfilled or available for a production process or activity to take place.
-
E.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24559af48819092e4b466778b07e2 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.