Triple
T19209202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aymaran languages |
E480312
|
entity |
| Predicate | familyCode |
P134982
|
FINISHED |
| Object | aym |
—
|
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: aym | Statement: [Aymaran languages, familyCode, aym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyCode Context triple: [Aymaran languages, familyCode, aym]
-
A.
familyCodeName
Indicates a designated code name used to identify or refer to a family unit or family-related grouping.
-
B.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
-
C.
familyClass
Indicates that an entity belongs to, or is categorized within, a particular family grouping or class in a familial or taxonomic hierarchy.
-
D.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
E.
familySaved
Indicates that one entity has rescued, protected, or preserved the well-being or survival of another entity’s family.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a000188190afb762ea24bc3deb |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:20 p.m.