Triple
T5738331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 368 |
E126553
|
entity |
| Predicate | laysDown |
P38948
|
FINISHED |
| Object | procedure for amendment of the Constitution |
—
|
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: procedure for amendment of the Constitution | Statement: [Article 368, laysDown, procedure for amendment of the Constitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laysDown Context triple: [Article 368, laysDown, procedure for amendment of the Constitution]
-
A.
laidDown
Indicates that an entity places or sets another entity down into a resting or horizontal position.
-
B.
laidDownAs
chosen
Indicates that one entity has been formally established, stipulated, or prescribed as a rule, principle, or condition for another.
-
C.
laidDownBy
Indicates that something was established, created, or set as a rule, principle, or foundation by a particular agent.
-
D.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
E.
laidDownPlace
Indicates the location where an entity was laid down or placed.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255c8c308190821f968ec41c5078 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.