Triple
T7237795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amstelhof |
E155274
|
entity |
| Predicate | usedAsRetirementHomeUntil |
P75951
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Amstelhof, usedAsRetirementHomeUntil, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRetirementHomeUntil Context triple: [Amstelhof, usedAsRetirementHomeUntil, 2007]
-
A.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
B.
usedAsResidenceAgainBy
Indicates that something previously used as a residence is once more being used as a residence by a particular entity.
-
C.
retired
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
-
D.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
E.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
- F. None of above. chosen
Provenance (4 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.