Triple
T27917686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romblon dialect |
E706117
|
entity |
| Predicate | hasVocabularyOverlapWith |
P11829
|
FINISHED |
| Object | Hiligaynon language |
—
|
NE NERFINISHED |
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 language | Statement: [Romblon dialect, hasVocabularyOverlapWith, Hiligaynon language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocabularyOverlapWith Context triple: [Romblon dialect, hasVocabularyOverlapWith, Hiligaynon language]
-
A.
hasVocabularyFrom
Indicates that one entity’s vocabulary, terminology, or set of terms is derived from, based on, or taken from another entity.
-
B.
hasDistinctVocabulary
Indicates that one entity’s vocabulary is different or distinguishable from that of another entity.
-
C.
hasCommonLoanwordsFrom
Indicates that two languages share loanwords that originate from the same source language.
-
D.
hasLexicalSimilarityWith
chosen
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
-
E.
isPartOfVocabulary
Indicates that something belongs to or is included within a particular vocabulary or defined set of terms.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 6:54 p.m.