Triple
T24415544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bima script |
E615572
|
entity |
| Predicate | languageFamilyOfLanguageWritten |
P17999
|
FINISHED |
| Object | Austronesian languages |
—
|
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: Austronesian languages | Statement: [Bima script, languageFamilyOfLanguageWritten, Austronesian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyOfLanguageWritten Context triple: [Bima script, languageFamilyOfLanguageWritten, Austronesian languages]
-
A.
languageFamilyWritten
chosen
Indicates that one language family is represented or recorded in a particular written form or script.
-
B.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
C.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
D.
languageFamilyOfWork
Indicates that a work belongs to or is classified under a particular language family.
-
E.
languageFamilyUsedFor
Indicates that a particular language family is employed or utilized for a specific purpose, context, or function.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29584d7b88190b35843d3c4e81e03 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.