Triple

T4491349
Position Surface form Disambiguated ID Type / Status
Subject Singleton Shire E100579 entity
Predicate hasSeat P3522 FINISHED
Object Singleton E72877 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: Singleton | Statement: [Singleton Shire, hasSeat, Singleton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Singleton
Context triple: [Singleton Shire, hasSeat, Singleton]
  • A. Singleton chosen
    Singleton is a town in the Hunter Region of New South Wales, Australia, known for its coal mining, agriculture, and proximity to the Hunter Valley wine region.
  • B. Mono
    Mono is a Native American language of the Numic branch of the Uto-Aztecan language family, traditionally spoken in parts of California.
  • C. Mono
    Mono is an open-source, cross-platform implementation of Microsoft's .NET framework that enables running .NET applications on multiple operating systems.
  • D. Solo
    Solo is a city in Central Java, Indonesia, renowned as a major center of traditional Javanese culture and batik craftsmanship.
  • E. Solo
    Solo is a 2018 Star Wars anthology film that explores the early adventures and origins of the iconic smuggler Han Solo.
  • 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_69bd43cdf15081909a4fa2585ff63b3e completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd556e69f88190b9c16afc2afcdbef completed March 20, 2026, 2:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69bd6f8190e88190aec651ac9fe9ef92 completed March 20, 2026, 4:02 p.m.
Created at: March 20, 2026, 12:59 p.m.