Triple
T434110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiligaynon language |
E9774
|
entity |
| Predicate | hasEthnologueCode |
P8719
|
FINISHED |
| Object | hil |
—
|
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: hil | Statement: [Hiligaynon language, hasEthnologueCode, hil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEthnologueCode Context triple: [Hiligaynon language, hasEthnologueCode, hil]
-
A.
hasISO6393Code
chosen
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
B.
hasGlottologName
Indicates that an entity is associated with a specific name as recorded in the Glottolog linguistic database.
-
C.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
-
D.
isCulturalLanguageOf
Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
-
E.
hasLanguageCodeOnWikipedia
Indicates that a particular language is represented on Wikipedia by a specific language code.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef0a008c8190ae0aa25e4df9c35f |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edda55e88190b7c17ba94d7df1ce |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.