Triple
T4948508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther’s exile at Wartburg Castle |
E111108
|
entity |
| Predicate | hasAssociatedBuildingType |
P50464
|
FINISHED |
| Object | medieval hilltop castle |
—
|
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: medieval hilltop castle | Statement: [Luther’s exile at Wartburg Castle, hasAssociatedBuildingType, medieval hilltop castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedBuildingType Context triple: [Luther’s exile at Wartburg Castle, hasAssociatedBuildingType, medieval hilltop castle]
-
A.
containsBuildingType
chosen
Indicates that a location or area includes at least one building of the specified type.
-
B.
hasBuildingHeightType
Indicates the classification or type used to characterize the height of a building in the relationship.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
hasBuildingComponent
Indicates that one entity includes, contains, or is composed of another entity as a physical building component.
-
E.
belongsToBuildingComplex
Indicates that one building or structure is part of, or included within, a larger building complex.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7166bb6c8190a40775ac8bb723a8 |
completed | March 20, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.