Triple
T20891588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Abbey of Burtscheid |
E514419
|
entity |
| Predicate | buildingsCurrentlyUsedAs |
P128371
|
FINISHED |
| Object | parish churches |
—
|
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: parish churches | Statement: [Imperial Abbey of Burtscheid, buildingsCurrentlyUsedAs, parish churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingsCurrentlyUsedAs Context triple: [Imperial Abbey of Burtscheid, buildingsCurrentlyUsedAs, parish churches]
-
A.
buildingUsedBy
Indicates that a particular building is utilized or occupied by a specified entity for some purpose.
-
B.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
C.
currentBuildings
Indicates that certain buildings are presently existing, active, or in use at a given time or context.
-
D.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
E.
buildings
chosen
Indicates that one or more buildings are associated with, located at, or relevant to the referenced 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05e307081908f1d044e877017ec |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.