Triple
T33018693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Short Creek community |
E844844
|
entity |
| Predicate | familyNorms |
P180207
|
FINISHED |
| Object | highBirthRates |
—
|
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: highBirthRates | Statement: [Short Creek community, familyNorms, highBirthRates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNorms Context triple: [Short Creek community, familyNorms, highBirthRates]
-
A.
cultFamily
Indicates that one entity is a family member of another within the context of a cult or cult-like group.
-
B.
traditionalFamily
chosen
Indicates a relationship where individuals are connected within a conventional family structure, typically characterized by established roles and norms based on long-standing cultural or societal expectations.
-
C.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
D.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
E.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:23 a.m.