Triple
T1332388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermitage Amsterdam |
E28671
|
entity |
| Predicate | buildingOriginalFunction |
P4098
|
FINISHED |
| Object | home for the elderly |
—
|
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: home for the elderly | Statement: [Hermitage Amsterdam, buildingOriginalFunction, home for the elderly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingOriginalFunction Context triple: [Hermitage Amsterdam, buildingOriginalFunction, home for the elderly]
-
A.
originalFunction
chosen
Indicates that one entity serves as the initial or primary function from which another function or behavior is derived or defined.
-
B.
originalBuildingConstructed
Indicates that a particular building was initially constructed in its original form or configuration.
-
C.
hasBuildingFunction
Indicates that a building is used for or serves a particular function or purpose.
-
D.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
-
E.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e7f1388190a6e4eb65a7997380 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.