Triple
T34729732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn Lake Trails, El Dorado County, California, United States |
E1001173
|
entity |
| Predicate | hasCommunityRules |
P205534
|
FINISHED |
| Object | CC&Rs |
—
|
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: CC&Rs | Statement: [Auburn Lake Trails, El Dorado County, California, United States, hasCommunityRules, CC&Rs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunityRules Context triple: [Auburn Lake Trails, El Dorado County, California, United States, hasCommunityRules, CC&Rs]
-
A.
hasCommunityControl
Indicates that authority or decision-making power over something is held collectively by a local community or community-based group.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasCommunityType
Indicates that an entity is associated with or classified under a particular type or category of community.
-
D.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
E.
hasGlobalCommunity
Indicates that an entity is associated with or participates in a worldwide community or network of people.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.