Triple
T34413699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barangay XI |
E883342
|
entity |
| Predicate | usesCommonLocalLanguage |
P115774
|
FINISHED |
| Object | Hiligaynon |
—
|
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: Hiligaynon | Statement: [Barangay XI, usesCommonLocalLanguage, Hiligaynon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommonLocalLanguage Context triple: [Barangay XI, usesCommonLocalLanguage, Hiligaynon]
-
A.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
B.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
C.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
D.
languageUsedInLocality
chosen
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
E.
hasCommonTranslationLanguage
Indicates that two entities share at least one language into which both can be or have been translated.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:59 a.m.