Triple
T31264778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tannenberg (Führerhauptquartier) |
E797221
|
entity |
| Predicate | leaderUsingHeadquarters |
P180164
|
FINISHED |
| Object | Adolf Hitler |
—
|
NE NERFINISHED |
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: Adolf Hitler | Statement: [Tannenberg (Führerhauptquartier), leaderUsingHeadquarters, Adolf Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderUsingHeadquarters Context triple: [Tannenberg (Führerhauptquartier), leaderUsingHeadquarters, Adolf Hitler]
-
A.
isBlockHeadquartersOf
Indicates that a particular block serves as the main headquarters location for a specified entity.
-
B.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the specified place.
-
C.
zoneHeadquarter
Indicates that an entity serves as the main administrative or coordinating headquarters for a specified zone or region.
-
D.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
E.
hasHeadquartersRoleFor
Indicates that an entity holds a specific role or position within the headquarters of another entity.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 29, 2026, 9:12 p.m.