Triple

T23025368
Position Surface form Disambiguated ID Type / Status
Subject Axminster E573293 entity
Predicate hasNearbyTown P3883 FINISHED
Object Chard 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: Chard | Statement: [Axminster, hasNearbyTown, Chard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chard
Context triple: [Axminster, hasNearbyTown, Chard]
  • A. Chard chosen
    Chard is a historic market town in Somerset, England, often noted for its claim as the birthplace of powered flight and as one of the county’s southernmost towns.
  • B. Kale
    Kale is a small irregular moon of Jupiter belonging to the planet’s distant, retrograde outer satellite group.
  • C. Kale
    Kale is a town in Myanmar’s Sagaing Region, known as a local commercial and transport hub in the country’s northwest.
  • D. Kale
    Kale is a district-level administrative area within Turkey, known for its location in Malatya Province in the Eastern Anatolia region.
  • E. Kale
    Kale is a town and district in Turkey’s Antalya Province, historically known as Demre and famed for its association with Saint Nicholas and ancient Myra.
  • 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847c671c8190a8095051d8c3cf93 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.