Triple
T5504234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 79 of the Constitution of India |
E144399
|
entity |
| Predicate | typeOfProvision |
P65125
|
FINISHED |
| Object | structural provision |
—
|
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: structural provision | Statement: [Article 79 of the Constitution of India, typeOfProvision, structural provision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfProvision Context triple: [Article 79 of the Constitution of India, typeOfProvision, structural provision]
-
A.
introducedProvision
Indicates that an entity formally brought a specific provision, clause, or measure into effect or into consideration.
-
B.
enforcedProvision
Indicates that an authority or agent compelled compliance with a specific rule, term, or provision.
-
C.
notableProvision
Indicates that one entity is a significant or noteworthy clause, term, or condition contained within another entity, such as a document, agreement, or law.
-
D.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
E.
typeOfContract
Indicates the specific kind or category of contractual agreement that applies between the related entities.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0d21848190ae8c41561eca6342 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:32 p.m.