Triple

T34409986
Position Surface form Disambiguated ID Type / Status
Subject TEAL E883228 entity
Predicate notableRoute P22 FINISHED
Object Auckland–Nukuʻalofa
Auckland–Nukuʻalofa is an international air route linking Auckland, New Zealand, with Nukuʻalofa, the capital of Tonga, serving as a key connection between the two Pacific nations.
E2098901 NE 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: Auckland–Nukuʻalofa | Statement: [TEAL, notableRoute, Auckland–Nukuʻalofa]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Auckland–Nukuʻalofa
Triple: [TEAL, notableRoute, Auckland–Nukuʻalofa]
Generated description
Auckland–Nukuʻalofa is an international air route linking Auckland, New Zealand, with Nukuʻalofa, the capital of Tonga, serving as a key connection between the two Pacific nations.

Provenance (5 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_69f349c1f2208190a09a489bb8b2719d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f718bf8c38819087f287b5ea01f4d4 completed May 3, 2026, 9:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37212176dc819098f9531ce8eade43 completed June 20, 2026, 11:24 p.m.
NEDg Description generation batch_6a3721ea92a48190bb0fc6df5267138e completed June 20, 2026, 11:27 p.m.
NED2 Entity disambiguation (via description) batch_6a3722d05034819087a1399552af21cc completed June 20, 2026, 11:31 p.m.
Created at: May 1, 2026, 1:59 a.m.