Triple

T18350038
Position Surface form Disambiguated ID Type / Status
Subject Port of Tauranga Limited E439640 entity
Predicate stockTicker P1447 FINISHED
Object POT 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: POT | Statement: [Port of Tauranga Limited, stockTicker, POT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: POT
Context triple: [Port of Tauranga Limited, stockTicker, POT]
  • A. POT chosen
    POT is the stock ticker symbol for Port of Tauranga Limited, New Zealand’s largest and busiest port company.
  • B. POT
    POT was the former abbreviation for Norway’s domestic security and intelligence agency, responsible for counterterrorism and national security before it was reorganized and renamed.
  • C. POU
    POU is the IATA airport code for Hudson Valley Regional Airport, a public airport serving the Poughkeepsie area in New York’s Hudson Valley.
  • D. POG
    POG is the IATA airport code for the main airport serving Port-Gentil, a coastal city in Gabon.
  • E. POK
    POK is the National Rail station code for Pokesdown railway station in Bournemouth, England.
  • 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_69d8b918221c8190a9f7b563d64ac677 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e514f7700c8190ae220de870e69304 completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 10:37 a.m.