Triple
T18066121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maiduan |
E432296
|
entity |
| Predicate | endangeredLanguageFamily |
P129683
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maiduan, endangeredLanguageFamily, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangeredLanguageFamily Context triple: [Maiduan, endangeredLanguageFamily, true]
-
A.
endangeredLanguage
Indicates that a language is at risk of falling out of use and potentially becoming extinct due to having too few active speakers or insufficient intergenerational transmission.
-
B.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
C.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
-
D.
majorLanguageFamilies
Indicates that one entity is a primary or dominant language family to which the other entity (a language or group of languages) belongs.
-
E.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4cce97ce08190a2f8762ce545e091 |
completed | April 19, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.