Triple
T8601790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qualicum Beach |
E203693
|
entity |
| Predicate | isRetirementDestination |
P15935
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Qualicum Beach, isRetirementDestination, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRetirementDestination Context triple: [Qualicum Beach, isRetirementDestination, true]
-
A.
retiredTo
chosen
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.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
C.
appliesToRetirementStatus
Indicates that the subject is relevant or applicable specifically to an entity’s retirement status or condition.
-
D.
usedAsRetirementHomeUntil
Indicates that something served the function of a retirement home up to a specified time or date.
-
E.
plannedRetirement
Indicates that an entity has scheduled or intends to end its active role or service at a specified future time.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46da609881909a6d851915e8df14 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.