Triple
T22460146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Farquhar |
E555206
|
entity |
| Predicate | precededByInRole:ResidentOfSingapore |
P148281
|
FINISHED |
| Object | position created |
—
|
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: position created | Statement: [William Farquhar, precededByInRole:ResidentOfSingapore, position created]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByInRole:ResidentOfSingapore Context triple: [William Farquhar, precededByInRole:ResidentOfSingapore, position created]
-
A.
hasResidenceIn
Indicates that an entity lives or maintains a primary dwelling in a specified location.
-
B.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
C.
succeededByResidence
Indicates that one residence directly follows and replaces another as the primary place of dwelling for an entity.
-
D.
hasResidenceOn
Indicates that one entity’s place of residence is located on or along another entity, such as a street, road, or other linear feature.
-
E.
residedOn
Indicates that an entity lived or had its primary dwelling at a specific location during a certain period.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7eb5688190bd5e41d4d8189668 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:48 p.m.