Triple
T23097874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden Springs, Idaho |
E575942
|
entity |
| Predicate | communityIdentity |
P142109
|
FINISHED |
| Object | family-oriented |
—
|
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: family-oriented | Statement: [Hidden Springs, Idaho, communityIdentity, family-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communityIdentity Context triple: [Hidden Springs, Idaho, communityIdentity, family-oriented]
-
A.
communityType
Indicates the classification or category of community to which an entity belongs (e.g., urban, rural, online, professional).
-
B.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
-
C.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
D.
communityService
Indicates participation in activities intended to benefit or support a community, typically performed voluntarily or as a civic responsibility.
-
E.
communityTrait
chosen
Indicates that a group or community shares or is characterized by a particular trait or attribute.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de61c7c8190809920fa1071935f |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.