Triple

T21965018
Position Surface form Disambiguated ID Type / Status
Subject South Auckland E542435 entity
Predicate hasSubregion P285 FINISHED
Object Manurewa 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: Manurewa | Statement: [South Auckland, hasSubregion, Manurewa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manurewa
Context triple: [South Auckland, hasSubregion, Manurewa]
  • A. Manurewa chosen
    Manurewa is a large residential suburb in South Auckland, New Zealand, known for its diverse community and proximity to key transport links and amenities.
  • B. Enmelen
    Enmelen is a small rural settlement located in the remote, Arctic coastal region of Chukotka in Russia.
  • C. Mankoya
    Mankoya is a dialect of the Silozi language spoken by communities in parts of southwestern Zambia.
  • D. Maaninka
    Maaninka is a former rural municipality in eastern Finland, known for its lakes and agricultural landscape, that is now part of the city of Kuopio in the Northern Savonia region.
  • E. Mansaka
    Mansaka is an Austronesian language spoken by the indigenous Mansaka people of southeastern Mindanao in the Philippines.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12459e1848190aa8d4ccc97f434b8 completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.