Triple

T20993913
Position Surface form Disambiguated ID Type / Status
Subject Truro Cathedral E517094 entity
Predicate locatedIn P40 FINISHED
Object Truro 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: Truro | Statement: [Truro Cathedral, locatedIn, Truro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Truro
Context triple: [Truro Cathedral, locatedIn, Truro]
  • A. Truro
    Truro is a town in central Nova Scotia, Canada, known historically as a key regional transportation hub and service center.
  • B. Truro
    Truro is a small coastal town on outer Cape Cod in Massachusetts known for its scenic beaches, dunes, and historic Highland Light lighthouse.
  • C. Truro chosen
    Truro is the cathedral city and administrative centre of Cornwall in southwest England, known for its historic architecture and cultural institutions.
  • D. Bodmin
    Bodmin is a historic town in Cornwall, England, known for its moorland surroundings and landmarks such as Bodmin Jail and St Petroc's Church.
  • E. Helston
    Helston is a small historic market town in Cornwall, England, known for its traditional Flora Day festival and proximity to the Lizard Peninsula.
  • 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc1e75188190a97114238ea0b4f9 completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:50 p.m.