Triple
T34029057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiftsgymnasium Melk |
E872592
|
entity |
| Predicate | buildingLocatedWithin |
P40
|
FINISHED |
| Object | Melk Abbey complex |
—
|
NE NERFINISHED |
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: Melk Abbey complex | Statement: [Stiftsgymnasium Melk, buildingLocatedWithin, Melk Abbey complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingLocatedWithin Context triple: [Stiftsgymnasium Melk, buildingLocatedWithin, Melk Abbey complex]
-
A.
buildingLocatedInNeighborhood
Indicates that a specific building is situated within a particular neighborhood.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
seatBuildingLocatedIn
Indicates that the building serving as a seat (e.g., headquarters or main office) is geographically located within a specified area or place.
-
D.
locationInArchitecture
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
-
E.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.