Triple
T16225022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hauptwache |
E393821
|
entity |
| Predicate | historicalFunctionOfGuardhouse |
P122233
|
FINISHED |
| Object | city guardhouse |
—
|
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: city guardhouse | Statement: [Hauptwache, historicalFunctionOfGuardhouse, city guardhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalFunctionOfGuardhouse Context triple: [Hauptwache, historicalFunctionOfGuardhouse, city guardhouse]
-
A.
historicallyGuardedBy
Indicates that an entity was protected or defended by another entity during a past historical period.
-
B.
royalPalaceFormerFunction
Indicates the previous primary role or use that a royal palace served before its current function.
-
C.
courthouseHistoricUse
Indicates the historical function or role that a courthouse served in the past.
-
D.
historicallyHoused
Indicates that one entity served as a location or container for another entity at some time in the past.
-
E.
periodUsedAsExecutiveMansion
Indicates the time period during which a particular building served as an executive mansion or official residence of a head of government or state.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d24f9688190b670cfeb73332293 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.