Triple
T21472945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motu people |
E529776
|
entity |
| Predicate | hasDialectOrVariety |
P84576
|
FINISHED |
| Object | Hiri Motu |
—
|
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: Hiri Motu | Statement: [Motu people, hasDialectOrVariety, Hiri Motu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectOrVariety Context triple: [Motu people, hasDialectOrVariety, Hiri Motu]
-
A.
hasNumberOfDialects
Indicates the relationship between a language (or linguistic entity) and the count of distinct dialects it possesses.
-
B.
hasLinguisticVariety
chosen
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
C.
hasDialectContinuumWith
Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
-
D.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
E.
isDialectalBaseOf
Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea156dac819087c4594d022d3df6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:19 p.m.