Triple
T1780208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King City, Oregon |
E39272
|
entity |
| Predicate | hasRetirementCommunityOrigins |
P23364
|
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: [King City, Oregon, hasRetirementCommunityOrigins, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetirementCommunityOrigins Context triple: [King City, Oregon, hasRetirementCommunityOrigins, true]
-
A.
foundedCommunity
Indicates that an entity established or created a community, organization, or group.
-
B.
hasPlannedCommunity
chosen
Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
-
C.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
D.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
E.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.