Triple
T37945823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastian Kurz |
E946603
|
entity |
| Predicate | tookOfficeAsChancellor |
P157242
|
FINISHED |
| Object | 2017-12-18 |
—
|
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-12-18 | Statement: [Sebastian Kurz, tookOfficeAsChancellor, 2017-12-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOfficeAsChancellor Context triple: [Sebastian Kurz, tookOfficeAsChancellor, 2017-12-18]
-
A.
termStartAsChancellor
chosen
Indicates the date or point in time when an individual begins their term serving in the role of chancellor.
-
B.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
-
C.
servedAsHeadOfTheChancelleryFrom
Indicates that a person held the position of head of the chancellery starting from a specified date or time period.
-
D.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
-
E.
assumedOfficeAsPremier
Indicates that an individual formally took up and began serving in the role of premier.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.