Triple
T38649661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfgang Schüssel |
E938805
|
entity |
| Predicate | wasChancellorInPeriod |
P15399
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Wolfgang Schüssel, wasChancellorInPeriod, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasChancellorInPeriod Context triple: [Wolfgang Schüssel, wasChancellorInPeriod, early 2000s]
-
A.
servedAsHeadOfTheChancelleryFrom
Indicates that a person held the position of head of the chancellery starting from a specified date or time period.
-
B.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
-
C.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
-
D.
formerChancellor
chosen
Indicates that one entity previously held the position or role of chancellor of the other entity, but no longer does.
-
E.
servedAsHeadOfTheChancelleryUntil
Indicates that a person held the position of head of the chancellery up to a specified end date or time.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.