Triple

T5788125
Position Surface form Disambiguated ID Type / Status
Subject Ostend E128320 entity
Predicate hasDemonym P191 FINISHED
Object Ostender E128320 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: Ostender | Statement: [Ostend, hasDemonym, Ostender]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostender
Context triple: [Ostend, hasDemonym, Ostender]
  • A. Port of Dieppe
    The Port of Dieppe is a major French English Channel harbor known for its ferry connections, fishing activities, and marina facilities serving the town of Dieppe in Normandy.
  • B. Ostend chosen
    Ostend is a Belgian coastal city on the North Sea known for its beaches, port, and seaside tourism.
  • C. Port of Zeebrugge
    The Port of Zeebrugge is a major Belgian seaport on the North Sea, serving as a key hub for cargo, passenger traffic, and energy logistics in northwestern Europe.
  • D. Ruby Bay
    Ruby Bay is a coastal area known for its sandy beach and seaside recreation near the settlement of Elie in Scotland.
  • E. Nieuwpoort
    Nieuwpoort is a coastal town in West Flanders, Belgium, known for its historic harbor and its strategic role in World War I.
  • 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_69c0084450048190bc647b649a05136b completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02a5297c88190bd28adb2552a26f4 completed March 22, 2026, 5:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0981a002c8190ac8ed7407a80919c completed March 23, 2026, 1:32 a.m.
Created at: March 22, 2026, 3:51 p.m.