Triple
T24593781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lapuyan Subanen |
E608608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Subanen |
C45793
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regional variety of Subanen Context triple: [Lapuyan Subanen, instanceOf, regional variety of Subanen]
-
A.
Subanen language variety
chosen
A Subanen language variety is a specific regional or social form of the Subanen language spoken by Subanen communities in the Zamboanga Peninsula and surrounding areas of the southern Philippines, characterized by distinct phonological, lexical, and grammatical features.
-
B.
Ivatan language variety
A specific form or dialect of the Ivatan language, characterized by its unique phonological, lexical, and grammatical features within the Ivatan-speaking community.
-
C.
Visayan language variety
A Visayan language variety is a specific regional or social form of any language within the Visayan (Bisayan) subgroup of the Austronesian language family, characterized by distinct phonological, lexical, and grammatical features.
-
D.
Bikol language
The Bikol language is an Austronesian language (or group of closely related languages) spoken primarily in the Bicol Region of the Philippines, known for its distinct phonology and vocabulary while sharing many features with other Central Philippine languages.
-
E.
Tacanan language
The Tacanan language is a member of the Tacanan language family spoken by indigenous Tacana peoples of the western Amazon region, primarily in Bolivia and Peru.
- F. None of above.
Provenance (1 batch)
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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:30 a.m.