Triple
T31420432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grabeskirche |
E801514
|
entity |
| Predicate | stehtUnter |
P27209
|
FINISHED |
| Object | Status quo der Heiligen Stätten |
—
|
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: Status quo der Heiligen Stätten | Statement: [Grabeskirche, stehtUnter, Status quo der Heiligen Stätten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stehtUnter Context triple: [Grabeskirche, stehtUnter, Status quo der Heiligen Stätten]
-
A.
holdsUnder
chosen
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
B.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
C.
standsAt
Indicates that one entity is positioned upright at or near a specific location or reference point associated with another entity.
-
D.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
-
E.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:47 p.m.