Triple

T4042476
Position Surface form Disambiguated ID Type / Status
Subject Port of Newcastle E83982 entity
Predicate locatedIn P40 FINISHED
Object Newcastle E83982 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: Newcastle | Statement: [Port of Newcastle, locatedIn, Newcastle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newcastle
Context triple: [Port of Newcastle, locatedIn, Newcastle]
  • A. Newcastle
    Newcastle is a major industrial and commercial city in South Africa’s KwaZulu-Natal province, known for its manufacturing, coal mining, and regional service economy.
  • B. Newcastle
    Newcastle is a suburban city in King County, Washington, known for its residential neighborhoods, parks, and proximity to Bellevue and Seattle.
  • C. Newcastle
    Newcastle is a settlement within the Parish of St. Andrew, likely a small town or village in a predominantly rural Caribbean island parish.
  • D. Newcastle
    Newcastle is a seaside resort town in County Down, Northern Ireland, known for its beach and as a gateway to the Mourne Mountains.
  • E. Newcastle chosen
    Newcastle is a coastal city in New South Wales, Australia, known for its busy port, beaches, and 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_69aed92f7cf0819098e0539bdcc3767f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb5b65c08190ba3f340ed18737f8 completed March 9, 2026, 4:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5564d0fb881909ba645714be27b95 completed March 14, 2026, 12:36 p.m.
Created at: March 9, 2026, 3:37 p.m.