Triple
T31466731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori Language Commission |
E802737
|
entity |
| Predicate | recognisesLanguageAs |
P185658
|
FINISHED |
| Object | taonga |
—
|
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: taonga | Statement: [Māori Language Commission, recognisesLanguageAs, taonga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognisesLanguageAs Context triple: [Māori Language Commission, recognisesLanguageAs, taonga]
-
A.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
-
B.
recognizesLanguages
Indicates that an entity has the ability to identify, understand, or acknowledge one or more languages.
-
C.
canRecognizeAllLanguagesOf
Indicates that one entity has the ability to recognize every language associated with another entity.
-
D.
languageOfWorkRecognized
Indicates that a work is officially recognized as being created or expressed in a particular language.
-
E.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
- F. None of above. chosen
Provenance (4 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 30, 2026, 9:23 p.m.