Triple

T14733104
Position Surface form Disambiguated ID Type / Status
Subject Lamont Park E346129 entity
Predicate locatedIn P40 FINISHED
Object Mount Pleasant E73115 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: Mount Pleasant | Statement: [Lamont Park, locatedIn, Mount Pleasant]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mount Pleasant
Context triple: [Lamont Park, locatedIn, Mount Pleasant]
  • A. Mount Pleasant chosen
    Mount Pleasant is a historic, culturally diverse residential neighborhood in Washington, D.C., known for its tree-lined streets, early 20th-century row houses, and vibrant local commerce.
  • B. Mount Pleasant
    Mount Pleasant is a suburban town in Westchester County, New York, known for its residential communities and proximity to major reservoirs and parklands.
  • C. Mount Pleasant
    Mount Pleasant is a prominent hill and scenic overlook in Rising Park, known for its panoramic views of the surrounding area.
  • D. Mount Pleasant
    Mount Pleasant is a rugby league stadium in Batley, West Yorkshire, England, known for its steep terraced slope and long association with the Batley Bulldogs.
  • E. Mount Pleasant
    Mount Pleasant is a residential neighbourhood within the town of Bedworth in Warwickshire, England.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec72ea9348190817efcdaa973d7f7 completed April 14, 2026, 11:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb8bcc188190901e3f692fd8fbf9 completed May 8, 2026, 3:04 p.m.
Created at: April 10, 2026, 1:29 a.m.