Triple
T32110295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangaian Māori |
E820100
|
entity |
| Predicate | closelyRelatedDialectOf |
P78566
|
FINISHED |
| Object | Cook Islands Māori |
—
|
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: Cook Islands Māori | Statement: [Mangaian Māori, closelyRelatedDialectOf, Cook Islands Māori]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closelyRelatedDialectOf Context triple: [Mangaian Māori, closelyRelatedDialectOf, Cook Islands Māori]
-
A.
closelyAssociatedLanguage
Indicates that one language is closely connected to another, such as through frequent co-use, mutual influence, or strong cultural or regional association.
-
B.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
C.
isDialectalBaseOf
Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
-
D.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in another dialect.
-
E.
relatedDialect
chosen
Indicates that one dialect has a recognized linguistic relationship or close affinity to another dialect.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 12:27 a.m.