Triple
T9475142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | November 2015 Turkish general election |
E228496
|
entity |
| Predicate | previousYear |
P70716
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [November 2015 Turkish general election, previousYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousYear Context triple: [November 2015 Turkish general election, previousYear, 2015]
-
A.
previousElectionYear
chosen
Indicates the year in which the immediately preceding election for the same office, position, or body took place.
-
B.
chronologyPreviousYear
Indicates that one time-related entity occurs exactly one calendar year before another in a chronological sequence.
-
C.
previousSeason
Indicates that one season directly precedes another in chronological order within the same series or competition.
-
D.
cededYear
Indicates the year in which control, ownership, or sovereignty over something was formally transferred from one party to another.
-
E.
previousWorkReleaseYear
Indicates the year in which an earlier or prior work in a sequence or related set was released.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ff39f48819087e696c2c1ffe638 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.