Triple
T25166906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warlpiri language |
E630203
|
entity |
| Predicate | hasCreoleRelatedVariety |
P84576
|
FINISHED |
| Object | Light Warlpiri |
—
|
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: Light Warlpiri | Statement: [Warlpiri language, hasCreoleRelatedVariety, Light Warlpiri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCreoleRelatedVariety Context triple: [Warlpiri language, hasCreoleRelatedVariety, Light Warlpiri]
-
A.
hasCreoleLanguage
Indicates that an entity possesses, uses, or is associated with a creole language.
-
B.
languageFamilyOfMajorCreole
Indicates that a given language family is the primary source or base language group from which a particular major creole language is derived.
-
C.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
D.
hasLinguisticVariety
chosen
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
E.
hasDialectalCounterpart
Indicates that one linguistic form has a corresponding equivalent or variant in 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 12:17 p.m.