Triple
T12724504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankanaey |
E304067
|
entity |
| Predicate | autonymVariant |
P57538
|
FINISHED |
| Object | Kankana-ey |
—
|
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: Kankana-ey | Statement: [Kankanaey, autonymVariant, Kankana-ey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonymVariant Context triple: [Kankanaey, autonymVariant, Kankana-ey]
-
A.
hasEthnonymVariant
chosen
Indicates that one ethnonym is an alternative or variant form of another ethnonym referring to the same ethnic group.
-
B.
autonymLanguageCode
Indicates that the associated language code is the one used by a language to refer to itself (its autonym).
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
isEndonym
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
E.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:25 p.m.