Triple
T8475605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königsbau |
E200382
|
entity |
| Predicate | isPartOfHistoricResidence |
P69638
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Königsbau, isPartOfHistoricResidence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfHistoricResidence Context triple: [Königsbau, isPartOfHistoricResidence, true]
-
A.
residenceHistoric
Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
-
B.
historicallyAssociatedHouse
Indicates that there is a historical connection or association between an entity and a particular house, such as residence, ownership, or significant events tied to that location.
-
C.
locatedInHistoricSite
chosen
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
D.
isHistoricPlace
Indicates that a place holds recognized historical significance, often due to its age, events, or cultural importance.
-
E.
historicallyHoused
Indicates that one entity served as a location or container for another entity at some time in the past.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f89e0081909e74beb7c8f55653 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.