Triple

T17672904
Position Surface form Disambiguated ID Type / Status
Subject Zeelandbrug E440570 entity
Predicate previouslyWorldsLongest P128497 FINISHED
Object yes 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: yes | Statement: [Zeelandbrug, previouslyWorldsLongest, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previouslyWorldsLongest
Context triple: [Zeelandbrug, previouslyWorldsLongest, yes]
  • A. heldLongestSpanRecordUntil
    Indicates that one entity held the record for the longest continuous span of time in some domain or metric, up until a specified endpoint or event.
  • B. wasWorldRecordFor
    Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
  • C. heldLongestSpanRecordFrom
    Indicates that one entity held a particular record for the longest continuous time span starting from another specified entity’s tenure.
  • D. previousWorldRecordLocation
    Indicates the location where the immediately preceding world record for a given event or category was set.
  • E. heldWorldsLargestTitleUntil
    Indicates that an entity held the distinction of being the world’s largest in a particular category up to a specified point in time.
  • F. None of above. chosen

Provenance (4 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f6aa64081908c9a82128a5a9024 completed April 19, 2026, 6 a.m.
PD Predicate disambiguation batch_69e3cde007d8819090dd92eea9f022cc completed April 18, 2026, 6:30 p.m.
PDg Predicate description generation batch_69e3cfaac2b881909e1140339eb1a0dd completed April 18, 2026, 6:38 p.m.
Created at: April 10, 2026, 10 a.m.