Triple

T857659
Position Surface form Disambiguated ID Type / Status
Subject Delta Works E18527 entity
Predicate hasPart P35 FINISHED
Object Oesterdam E14471 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: Oesterdam | Statement: [Delta Works, hasPart, Oesterdam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oesterdam
Context triple: [Delta Works, hasPart, Oesterdam]
  • A. Oesterdam chosen
    Oesterdam is a major Dutch dam and storm surge barrier that forms part of the Delta Works coastal defense system in the Rhine–Meuse–Scheldt delta.
  • B. German tanker Altmark
    The German tanker Altmark was a World War II-era naval auxiliary ship of Nazi Germany, best known for its role in the 1940 Altmark Incident involving the rescue of British prisoners in Norwegian waters.
  • C. Emden
    Emden is a historic port city in northwestern Germany known for its maritime industry and location near the North Sea.
  • D. Dutch Navy ship HNLMS De Ruyter
    HNLMS De Ruyter is a Royal Netherlands Navy warship named in honor of the famed 17th-century Dutch admiral Michiel de Ruyter.
  • E. M/V Columbia
    M/V Columbia is a mainline passenger and vehicle ferry that serves as one of the flagship vessels of the Alaska Marine Highway System, operating along coastal routes in Alaska and the Pacific Northwest.
  • 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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac4d47508190b48d944aa2d881bf completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7b8494840819091324bf603ff8d7c completed March 4, 2026, 4:42 a.m.
Created at: March 1, 2026, 7:39 p.m.