Triple
T2788588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odilo Globocnik |
E61870
|
entity |
| Predicate | startOfTermAsGauleiterOfVienna |
P43588
|
FINISHED |
| Object | 1938 |
—
|
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: 1938 | Statement: [Odilo Globocnik, startOfTermAsGauleiterOfVienna, 1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfTermAsGauleiterOfVienna Context triple: [Odilo Globocnik, startOfTermAsGauleiterOfVienna, 1938]
-
A.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
-
B.
startTimeAsElectorOfBavaria
Indicates the point in time when an entity began holding the position or role of Elector of Bavaria.
-
C.
reignEndAsEmperorOfAustria
Indicates the date or event marking when an individual’s tenure as Emperor of Austria came to an end.
-
D.
commandedByHabsburg
Indicates that the subject is under the military or political command or authority of a member or representative of the Habsburg dynasty.
-
E.
servedAsHeadOfTheChancelleryFrom
Indicates that a person held the position of head of the chancellery starting from a specified date or time period.
- F. None of above. chosen
Provenance (4 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 9:58 p.m.