Triple
T6328975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bugotu language |
E141927
|
entity |
| Predicate | hasLanguageFamilyRoot |
P30710
|
FINISHED |
| Object | Proto-Austronesian language |
—
|
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: Proto-Austronesian language | Statement: [Bugotu language, hasLanguageFamilyRoot, Proto-Austronesian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageFamilyRoot Context triple: [Bugotu language, hasLanguageFamilyRoot, Proto-Austronesian language]
-
A.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
B.
derivedFromLanguageFamily
chosen
Indicates that one language originates from, or historically descends from, a particular language family.
-
C.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
D.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
E.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.