Triple
T13771634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monument to Maria Christina of Austria |
E330893
|
entity |
| Predicate | locatedInTheChurch |
P110884
|
FINISHED |
| Object | Nave of the Augustinerkirche |
—
|
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: Nave of the Augustinerkirche | Statement: [Monument to Maria Christina of Austria, locatedInTheChurch, Nave of the Augustinerkirche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheChurch Context triple: [Monument to Maria Christina of Austria, locatedInTheChurch, Nave of the Augustinerkirche]
-
A.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
B.
housedInChapel
Indicates that something is located, kept, or contained within a chapel.
-
C.
floorLocationOfChurch
Indicates the specific floor or level within a building where the church is located.
-
D.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
E.
roofLocationOfChurch
Indicates that one entity is the roof that belongs to or is located on a church.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0235aea881909ab4c721db081b00 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:10 p.m.