Triple

T2417856
Position Surface form Disambiguated ID Type / Status
Subject MacArthur Causeway E52347 entity
Predicate hasBridgeSections P17089 FINISHED
Object multiple LITERAL 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: multiple | Statement: [MacArthur Causeway, hasBridgeSections, multiple]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBridgeSections
Context triple: [MacArthur Causeway, hasBridgeSections, multiple]
  • A. hasBridgeSection chosen
    Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
  • B. hasNumberOfBridges
    Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
  • C. hasBridgeTo
    Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
  • D. hasPassengerBridge
    Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
  • E. hasMajorBridge
    Indicates that one entity possesses or includes a primary or significant bridge associated with it.
  • F. None of above.

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_69ab495622948190bc6bc6e4cddaf645 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc9f342e88190a430b02842ded418 completed March 7, 2026, 6:47 a.m.
PD Predicate disambiguation batch_69abc5a889948190b77de4ef6ac815a8 completed March 7, 2026, 6:28 a.m.
Created at: March 6, 2026, 9:42 p.m.