Triple
T21620159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution (Forty-second Amendment) Act, 1976 |
E533554
|
entity |
| Predicate | insertedPart |
P90748
|
FINISHED |
| Object | Part IVA |
—
|
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: Part IVA | Statement: [Constitution (Forty-second Amendment) Act, 1976, insertedPart, Part IVA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insertedPart Context triple: [Constitution (Forty-second Amendment) Act, 1976, insertedPart, Part IVA]
-
A.
proposedPart
Indicates that one entity has been suggested or put forward to serve as a component or element of another entity.
-
B.
insertedUnder
Indicates that one entity has been placed or positioned beneath another entity, typically in a physical or structural context.
-
C.
introducedPart
Indicates that one entity has brought another entity into existence, use, or awareness as a component or element of something.
-
D.
replacedPartOf
Indicates that one entity has taken the place of another entity as a component or part within a larger whole.
-
E.
insertedBy
chosen
Indicates that one entity was placed, added, or introduced into another entity or context by a specific agent or process.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3baeeae48190b78583b3bec8ee33 |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.