Triple

T37420659
Position Surface form Disambiguated ID Type / Status
Subject Southern Cross E929840 entity
Predicate hasAirport P105 FINISHED
Object Southern Cross Airport
Southern Cross Airport is a small regional airfield serving the town of Southern Cross in Western Australia, primarily used for general aviation and charter flights.
E2227362 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: Southern Cross Airport | Statement: [Southern Cross, hasAirport, Southern Cross Airport]
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: Southern Cross Airport
Triple: [Southern Cross, hasAirport, Southern Cross Airport]
Generated description
Southern Cross Airport is a small regional airfield serving the town of Southern Cross in Western Australia, primarily used for general aviation and charter flights.

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_69f76ebf0f288190ba198a78341613b8 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8da987508190b5e442b390a5ed24 completed May 6, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40824d12448190bab30cfad9823c2c completed June 28, 2026, 2:09 a.m.
NEDg Description generation batch_6a408492e5ec8190bd0107aaac82e291 completed June 28, 2026, 2:18 a.m.
NED2 Entity disambiguation (via description) batch_6a4084fb37f881909e2a7db9dc234507 completed June 28, 2026, 2:20 a.m.
Created at: May 3, 2026, 4:16 p.m.