Triple

T9861780
Position Surface form Disambiguated ID Type / Status
Subject Pilning E239730 entity
Predicate locatedNear P294 FINISHED
Object Aust E345934 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: Aust | Statement: [Pilning, locatedNear, Aust]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aust
Context triple: [Pilning, locatedNear, Aust]
  • A. Aust chosen
    Aust is a small village in South Gloucestershire, England, situated near the Severn Estuary and known historically for its ferry crossing and proximity to the Severn Bridge.
  • B. AUS
    AUS is the three-letter IATA airport code for Austin–Bergstrom International Airport, the primary commercial airport serving Austin, Texas.
  • C. AUS
    AUS is the governing body for university-level varsity sports in Atlantic Canada, organizing intercollegiate athletic competitions among its member institutions.
  • D. AUS
    AUS is the three-letter country code for Australia, the host nation of the 2000 Summer Olympics in Sydney.
  • E. Aus
    Aus is a small town in southern Namibia known for its desert landscapes, World War I history, and nearby feral horses.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84e6493081909cf58c8d42ea856b completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3b6aa108190978f1c0cdc0f45a0 completed April 2, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e4411a9481909657f522af7500ac completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:35 p.m.