Triple
T14161959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drakesteijn |
E350969
|
entity |
| Predicate | usedAsPrimaryResidenceFrom |
P98906
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Drakesteijn, usedAsPrimaryResidenceFrom, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPrimaryResidenceFrom Context triple: [Drakesteijn, usedAsPrimaryResidenceFrom, 1963]
-
A.
usedAsOfficialResidenceSince
Indicates that an entity has served as the formally designated official residence of another entity starting from a specified point in time.
-
B.
usedAsHomeUntil
Indicates that something served as a home for an entity up to a specified end time or event.
-
C.
usedAsHomeFrom
chosen
Indicates that something served as a home or dwelling for a specified entity starting from a particular point in time.
-
D.
usedAtResidence
Indicates that an object, resource, or service is utilized within or for the purposes of a particular residence.
-
E.
usedAsResidenceAgainBy
Indicates that something previously used as a residence is once more being used as a residence by a particular 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de613a4a2081908fd51bf4b4d82b6c |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.