Triple

T8221767
Position Surface form Disambiguated ID Type / Status
Subject Fort Lee Historic Park E192078 entity
Predicate municipality P852 FINISHED
Object Fort Lee E36610 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: Fort Lee | Statement: [Fort Lee Historic Park, municipality, Fort Lee]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Lee
Context triple: [Fort Lee Historic Park, municipality, Fort Lee]
  • A. Fort Lee
    Fort Lee is a major U.S. Army installation in Virginia that has historically served as a key center for logistics, sustainment, and support training.
  • B. Fort Lee, New Jersey chosen
    Fort Lee, New Jersey is a borough in Bergen County located at the western terminus of the George Washington Bridge, known as a historic gateway between New Jersey and New York City.
  • C. Parlin
    Parlin is a residential community and unincorporated neighborhood within the borough of Sayreville in Middlesex County, New Jersey.
  • D. Hackensack
    Hackensack were a Lenape Native American group from the region of present-day northern New Jersey, known for their involvement in early 17th-century conflicts with Dutch colonists.
  • E. Hoboken
    Hoboken is a district of the Belgian city of Antwerp, known for its residential character and industrial areas along the Scheldt River.
  • 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_69ca82c9a8ac81908b011c38698456e4 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb77c9680081909000fde3c9ae83ea completed March 31, 2026, 7:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69cef2b985888190a692f52cf5b93a80 completed April 2, 2026, 10:50 p.m.
Created at: March 30, 2026, 5:45 p.m.