Triple
T17235303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence Park, Toronto |
E418341
|
entity |
| Predicate | housingTypeIncludes |
P119140
|
FINISHED |
| Object | detached houses |
—
|
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: detached houses | Statement: [Lawrence Park, Toronto, housingTypeIncludes, detached houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: housingTypeIncludes Context triple: [Lawrence Park, Toronto, housingTypeIncludes, detached houses]
-
A.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
B.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
-
C.
typeOfHouse
chosen
Indicates the specific category or kind of house associated with an entity (e.g., apartment, detached house, townhouse).
-
D.
housingForm
Indicates the type or structure of housing associated with an entity (e.g., apartment, single-family home, dormitory).
-
E.
houseTypeLower
Indicates that one entity has a house type that is considered lower or less than another entity’s house type in some defined ordering or hierarchy.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfb04e481909f4ee3ed31fffe10 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.