Triple

T20037403
Position Surface form Disambiguated ID Type / Status
Subject Swisshelm Park E497311 entity
Predicate near P350 FINISHED
Object Swissvale 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: Swissvale | Statement: [Swisshelm Park, near, Swissvale]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Swissvale
Context triple: [Swisshelm Park, near, Swissvale]
  • A. Swissvale, Pennsylvania chosen
    Swissvale, Pennsylvania is a residential borough in Allegheny County near Pittsburgh, known for its historic neighborhoods and proximity to major urban amenities.
  • B. Monessen
    Monessen is a small industrial city in western Pennsylvania historically known for its steel production along the Monongahela River.
  • C. Wilkinsburg
    Wilkinsburg is a borough in Allegheny County, Pennsylvania, known as an inner-ring suburb directly east of Pittsburgh.
  • D. Bethel Park
    Bethel Park is a suburban municipality in southwestern Pennsylvania, located just south of Pittsburgh.
  • E. Aliquippa
    Aliquippa is a small industrial city in western Pennsylvania known historically for its steel production and location along the Ohio River.
  • 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_69da627278c88190babe4297a9df1236 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662e935ac8190900cdb4f0cfde505 completed April 20, 2026, 5:31 p.m.
Created at: April 11, 2026, 3:36 p.m.