Triple
T21667132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuvu languages |
E534751
|
entity |
| Predicate | areIndigenousLanguages |
P124195
|
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: [Manuvu languages, areIndigenousLanguages, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areIndigenousLanguages Context triple: [Manuvu languages, areIndigenousLanguages, true]
-
A.
mainIndigenousLanguage
Indicates the primary indigenous language predominantly used or spoken by a person, group, or within a specific context.
-
B.
isIndigenousLanguageGroup
chosen
Indicates that a language group originates from and is traditionally associated with the native or first peoples of a specific region or territory.
-
C.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
-
D.
isRecognizedAsIndigenousLanguage
Indicates that a language is officially acknowledged or accepted as belonging to an indigenous people or community.
-
E.
isOneOfMostSpokenIndigenousLanguagesIn
Indicates that a language ranks among the most widely spoken indigenous languages within a specified region or country.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0cf6208190a8bd9fa423c65a40 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:37 p.m.