Triple
T8760610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum Prinsenhof Delft |
E208186
|
entity |
| Predicate | hasBuildingUseHistory |
P2417
|
FINISHED |
| Object | former convent |
—
|
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: former convent | Statement: [Museum Prinsenhof Delft, hasBuildingUseHistory, former convent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingUseHistory Context triple: [Museum Prinsenhof Delft, hasBuildingUseHistory, former convent]
-
A.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
B.
buildingUsedSince
Indicates that a particular building has been in use starting from a specified point in time.
-
C.
hasFormerBuilding
Indicates that an entity previously occupied or used a different building, which is identified as its former building.
-
D.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
hasModernSiteUse
Indicates that an entity is currently used or functions in a particular way at a modern site or location.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5df9729481908679151988b76d2f |
completed | March 31, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.