Triple
T32161969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guaicuruan languages |
E821451
|
entity |
| Predicate | statusOfFamily |
P197421
|
FINISHED |
| Object | small language family |
—
|
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: small language family | Statement: [Guaicuruan languages, statusOfFamily, small language family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfFamily Context triple: [Guaicuruan languages, statusOfFamily, small language family]
-
A.
currentFamilyStatus
Indicates the present state or condition of an entity’s family situation or relationships.
-
B.
familySocialStatus
Indicates the social standing or class position associated with a person’s family within a society.
-
C.
macroFamilyStatus
Indicates the broad genealogical relationship between languages or language families at the macro-family level.
-
D.
familyNameStatus
Indicates the status or condition of a person's family name, such as whether it is current, former, changed, or otherwise designated.
-
E.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 1, 2026, 12:32 a.m.