Triple
T2646711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum Catharijneconvent |
E53800
|
entity |
| Predicate | usesBuildingType |
P1267
|
FINISHED |
| Object | monastery complex |
—
|
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: monastery complex | Statement: [Museum Catharijneconvent, usesBuildingType, monastery complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBuildingType Context triple: [Museum Catharijneconvent, usesBuildingType, monastery complex]
-
A.
usesBuilding
chosen
Indicates that one entity makes use of, occupies, or operates within a particular building.
-
B.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
D.
appliesToBuildingComplex
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable to an entire building complex rather than to individual buildings or units.
-
E.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91846b4819093a063c15e1ee6af |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.