Triple
T9775475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell, New Zealand |
E237234
|
entity |
| Predicate | hasLanguageOfIndigenousName |
P70102
|
FINISHED |
| Object | Māori |
—
|
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: Māori | Statement: [Russell, New Zealand, hasLanguageOfIndigenousName, Māori]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfIndigenousName Context triple: [Russell, New Zealand, hasLanguageOfIndigenousName, Māori]
-
A.
hasIndigenousLanguageRegion
Indicates that a region is associated with, or characterized by, the presence or use of one or more indigenous languages.
-
B.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
C.
hasIndigenousLanguageFamily
Indicates that an entity’s indigenous language belongs to, or is classified under, a particular language family.
-
D.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
hasEndonymLanguage
chosen
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1325a988190a07a3dc4dce41cb3 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.