Triple

T7584263
Position Surface form Disambiguated ID Type / Status
Subject Rombak Bridge E179566 entity
Predicate crosses P416 FINISHED
Object Rombaken E179566 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: Rombaken | Statement: [Rombak Bridge, crosses, Rombaken]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rombaken
Context triple: [Rombak Bridge, crosses, Rombaken]
  • A. Rombaken chosen
    Rombaken is a fjord in northern Norway, known as an inner branch of the Ofotfjord near the town of Narvik.
  • B. Rycken
    Rycken is a Dutch-origin surname historically borne by families such as that of Abraham Rycken in the Low Countries and early colonial America.
  • C. Rokkasen
    Rokkasen refers to the group of six celebrated classical Japanese waka poets of the early Heian period, renowned for their exemplary and influential verse.
  • D. Rommen
    Rommen is a neighborhood in Oslo, Norway, situated within the Søndre Nordstrand borough.
  • E. Rupbas
    Rupbas is a town located in the historic Braj cultural region of northern India, known for its traditional Braj heritage and proximity to major religious and historical sites.
  • 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_69c69f327db881909a21ae3b156f8ded completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f993cd0c8190864f801074625a32 completed March 27, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c86840abc08190b7ca9fb8e2968311 completed March 28, 2026, 11:46 p.m.
Created at: March 27, 2026, 3:52 p.m.