Triple

T9259009
Position Surface form Disambiguated ID Type / Status
Subject Hernando de Soto Bridge E222522 entity
Predicate alsoKnownAs P39 FINISHED
Object M Bridge E222522 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: M Bridge | Statement: [Hernando de Soto Bridge, alsoKnownAs, M Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M Bridge
Context triple: [Hernando de Soto Bridge, alsoKnownAs, M Bridge]
  • A. M Bridge chosen
    M Bridge is the common nickname for the Hernando de Soto Bridge, a steel through-arch bridge carrying Interstate 40 across the Mississippi River between Memphis, Tennessee, and West Memphis, Arkansas.
  • B. Z Bridge
    Z Bridge is a notable bridge spanning the Mutha River in Pune, India, serving as an important local transport link.
  • C. Multibus
    Multibus is an early Intel-developed computer bus standard widely used in 1980s workstations and embedded systems for modular expansion and peripheral connectivity.
  • D. Ada Bridge
    Ada Bridge is a prominent cable-stayed bridge in Belgrade, Serbia, known for its striking pylon design and role as a major traffic link across the Sava River.
  • E. UNIBUS
    UNIBUS is a pioneering computer bus architecture developed for Digital Equipment Corporation’s PDP series that unified memory and peripheral communications on a single shared system bus.
  • 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_69ca841e4cd481908e738c74e958eaea completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd0714317481908405f857a4f49e74 completed April 1, 2026, 11:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69d09bf225608190ade085302946dd8f completed April 4, 2026, 5:04 a.m.
Created at: March 30, 2026, 7:32 p.m.