Triple
T16666537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corachol language |
E404995
|
entity |
| Predicate | isIndigenousLanguageGroup |
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: [Corachol language, isIndigenousLanguageGroup, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIndigenousLanguageGroup Context triple: [Corachol language, isIndigenousLanguageGroup, true]
-
A.
isRecognizedAsIndigenousLanguage
Indicates that a language is officially acknowledged or accepted as belonging to an indigenous people or community.
-
B.
hasIndigenousLanguageFamily
Indicates that an entity’s indigenous language belongs to, or is classified under, a particular language family.
-
C.
isIndigenousLanguageNameOf
Indicates that a given name is the name of a language as expressed in an indigenous language.
-
D.
hasIndigenousLanguageSpoken
Indicates that an entity is associated with an indigenous language that is or was spoken by it or within its context.
-
E.
hasIndigenousLanguageRegion
Indicates that a region is associated with, or characterized by, the presence or use of one or more indigenous languages.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c9d9fc48190a8156c029668b544 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:18 a.m.