Triple

T8573507
Position Surface form Disambiguated ID Type / Status
Subject Long Bridge Park, Arlington E202986 entity
Predicate namedAfter P63 FINISHED
Object Long Bridge E35960 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: Long Bridge | Statement: [Long Bridge Park, Arlington, namedAfter, Long Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Long Bridge
Context triple: [Long Bridge Park, Arlington, namedAfter, Long Bridge]
  • A. Long Bridge chosen
    Long Bridge is a major railroad bridge over the Potomac River in Washington, D.C., carrying freight and passenger trains between the District of Columbia and Virginia.
  • B. Long Bridge
    Long Bridge is a notable bridge that serves as a key nearby landmark to Prague’s historic Green Gate.
  • C. Norfolk Bridge
    Norfolk Bridge is a historic road bridge spanning the River Adur in Shoreham-by-Sea, West Sussex, England.
  • D. Albert Bridge
    Albert Bridge is a historic and ornate road bridge over the River Thames in London, connecting Chelsea and Battersea.
  • E. Albert Bridge
    Albert Bridge is a historic road bridge in Belfast, Northern Ireland, known for carrying traffic across the River Lagan near the city centre.
  • 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_69ca8328ebe481909a8c038fa79959b4 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbea458c1081908e79bee2cbf97207 completed March 31, 2026, 3:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69d05bdc87fc8190a5ae0883742cb08c completed April 4, 2026, 12:31 a.m.
Created at: March 30, 2026, 6:21 p.m.