Triple

T822442
Position Surface form Disambiguated ID Type / Status
Subject Booderee National Park E17778 entity
Predicate hasAboriginalNameMeaning P1966 FINISHED
Object “bay of plenty” 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: “bay of plenty” | Statement: [Booderee National Park, hasAboriginalNameMeaning, “bay of plenty”]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAboriginalNameMeaning
Context triple: [Booderee National Park, hasAboriginalNameMeaning, “bay of plenty”]
  • A. meaningOfNativeName chosen
    Indicates that one entity specifies the semantic meaning or translation of another entity’s native-language name.
  • B. hasTraditionalOwner
    Indicates that an entity is recognized as the customary or ancestral owner or custodian of another entity, typically land, territory, or a cultural site.
  • C. hasEndonym
    Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
  • D. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • E. hasEnglishName
    Indicates that an entity is associated with a name expressed in the English language.
  • 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_69a4937bcaac8190a322524ac6f45a5a completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4ab976094819086d676404d745750 completed March 1, 2026, 9:11 p.m.
PD Predicate disambiguation batch_69a4aa76a7808190ac7fd9ba1a4cebcb completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:38 p.m.