Triple
T21306760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 134 of the Constitution of India |
E525217
|
entity |
| Predicate | sectionOrClause |
P3120
|
FINISHED |
| Object | Article 134(1)(a) |
—
|
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: Article 134(1)(a) | Statement: [Article 134 of the Constitution of India, sectionOrClause, Article 134(1)(a)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOrClause Context triple: [Article 134 of the Constitution of India, sectionOrClause, Article 134(1)(a)]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
sectionType
Indicates the specific kind or category of section that an entity belongs to or represents.
-
C.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
-
D.
sectionContext
Indicates that one element occurs within the contextual scope or environment defined by a particular section of a larger structure or document.
-
E.
isOpeningSectionOf
Indicates that one content segment functions as the initial or introductory section of another, larger work or structure.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa69b40819081e74c042e7cd105 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.