Triple

T33384226
Position Surface form Disambiguated ID Type / Status
Subject Ngāti Kurī E854867 entity
Predicate traditionalWaka P90582 FINISHED
Object Kurahaupō 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: Kurahaupō | Statement: [Ngāti Kurī, traditionalWaka, Kurahaupō]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalWaka
Context triple: [Ngāti Kurī, traditionalWaka, Kurahaupō]
  • A. otherGreatHaikuMasters
    Indicates that an entity is among the additional or alternative great haiku masters associated with another referenced entity.
  • B. hasWaka chosen
    Indicates that an entity possesses, contains, or is associated with a waka (such as a traditional canoe, vessel, or similarly defined object).
  • C. isTraditional
    Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
  • D. isTraditionalFormOf
    Indicates that one entity is the historically established or customary version from which another, typically more modern or variant, form is derived.
  • E. honkanStyle
    Indicates a relationship where something follows or exhibits the characteristics of the Honkan style (a specific stylistic or design convention).
  • 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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fedd5a5f4c8190acce88db56303703 completed May 9, 2026, 7:08 a.m.
PD Predicate disambiguation batch_69fed910b31c8190ae837163d146738d completed May 9, 2026, 6:49 a.m.
Created at: May 1, 2026, 1:35 a.m.