Triple
T10768618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodsworth Residence |
E254016
|
entity |
| Predicate | residenceModel |
P542
|
FINISHED |
| Object | independent-living focused residence |
—
|
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: independent-living focused residence | Statement: [Woodsworth Residence, residenceModel, independent-living focused residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceModel Context triple: [Woodsworth Residence, residenceModel, independent-living focused residence]
-
A.
residence
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
residenceType
chosen
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
depictsResidence
Indicates that one entity visually represents or portrays the place where another entity lives or resides.
-
D.
residenceUsedFor
Indicates that a particular residence is used for a specific purpose, function, or activity.
-
E.
architectOfResidence
Indicates that one entity is the architect responsible for designing the residence associated with another 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7322f9968819098b0ad54b913bfe4 |
completed | April 9, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.