Triple
T2986467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Turkey |
E80636
|
entity |
| Predicate | constitutionalReformYear |
P28679
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Government of Turkey, constitutionalReformYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalReformYear Context triple: [Government of Turkey, constitutionalReformYear, 2017]
-
A.
majorAmendmentYear
chosen
Indicates the year in which a significant or major amendment was made to something (such as a document, law, or agreement).
-
B.
lastConstitutionAdopted
Indicates that a particular constitution was the most recently adopted constitution of a given political entity or jurisdiction.
-
C.
constitutionalChange
Indicates a formal modification, addition, or removal of provisions within a constitution or foundational legal framework.
-
D.
majorAmendmentDate
Indicates the date on which a significant change or revision to something was formally made or took effect.
-
E.
constitutionalReformCreatedBy
Indicates that a specific constitutional reform was initiated, drafted, or brought into existence by a particular actor or entity.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.