Triple
T21500622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Azerbaijan |
E530463
|
entity |
| Predicate | amendedByReferendumOn |
P11741
|
FINISHED |
| Object | 2002-08-24 |
—
|
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: 2002-08-24 | Statement: [Constitution of Azerbaijan, amendedByReferendumOn, 2002-08-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amendedByReferendumOn Context triple: [Constitution of Azerbaijan, amendedByReferendumOn, 2002-08-24]
-
A.
proposedAmendment
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
B.
majorAmendmentDate
chosen
Indicates the date on which a significant change or revision to something was formally made or took effect.
-
C.
majorAmendment
Indicates that one entity makes a significant or substantial change to another entity, typically altering its core content, structure, or effect.
-
D.
constitutionalChange
Indicates a formal modification, addition, or removal of provisions within a constitution or foundational legal framework.
-
E.
amendmentYear
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea5be400819093e2b7e145254eab |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:24 p.m.