Triple

T6059813
Position Surface form Disambiguated ID Type / Status
Subject Lancaster and Fleetwood E135005 entity
Predicate mainSettlement P13187 FINISHED
Object Fleetwood E38809 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: Fleetwood | Statement: [Lancaster and Fleetwood, mainSettlement, Fleetwood]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fleetwood
Context triple: [Lancaster and Fleetwood, mainSettlement, Fleetwood]
  • A. Fleetwood
    Fleetwood is a residential neighborhood in the city of Mount Vernon, New York, known for its suburban character and proximity to New York City.
  • B. Fleetwood chosen
    Fleetwood is a coastal town and historic port in Lancashire, England, known for its maritime heritage and role as a ferry and fishing hub.
  • C. Shandon
    Shandon is a small village on the shores of Gare Loch in Argyll and Bute, Scotland, known for its scenic waterfront setting and residential character.
  • D. Shandon
    Shandon is a small rural community in California’s Central Coast region known for its agriculture and proximity to local vineyards and ranchlands.
  • E. Heywood
    Heywood is a town in Greater Manchester, England, historically part of Lancashire and known for its industrial heritage.
  • 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_69c00878d06881909ee78e88913bf890 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0571e479c8190bec0e1439b4cf68f completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c135761d0081908864f17234af11bd completed March 23, 2026, 12:43 p.m.
Created at: March 22, 2026, 4:10 p.m.