Triple

T15505547
Position Surface form Disambiguated ID Type / Status
Subject HMS Manchester E379070 entity
Predicate namedAfter P63 FINISHED
Object Manchester E114 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: Manchester | Statement: [HMS Manchester, namedAfter, Manchester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manchester
Context triple: [HMS Manchester, namedAfter, Manchester]
  • A. Manchester chosen
    Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
  • B. Manchester
    Manchester is a historic neighborhood on Pittsburgh’s North Side known for its 19th-century architecture and designation as a historic district.
  • C. Manchester
    Manchester is the most populous city in the U.S. state of New Hampshire and a major economic and cultural center for the region.
  • D. Manchester
    Manchester is a suburban town in central Connecticut known for its historic mills, shopping districts, and residential communities within the Greater Hartford area.
  • E. York
    York is a common English surname historically associated with the city of York in England and borne by various notable individuals and families.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcd5d948190b25a67a72ef980e9 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d4cf35c8190aa8d2db6dd744c3f completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 3:55 a.m.