Triple

T23799514
Position Surface form Disambiguated ID Type / Status
Subject Dunkerque E588629 entity
Predicate playsStrategicRoleIn P68592 FINISHED
Object Channel and North Sea maritime traffic 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: Channel and North Sea maritime traffic | Statement: [Dunkerque, playsStrategicRoleIn, Channel and North Sea maritime traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: playsStrategicRoleIn
Context triple: [Dunkerque, playsStrategicRoleIn, Channel and North Sea maritime traffic]
  • A. playsInRole
    Indicates that an entity performs or appears in a specific role within a production, event, or context.
  • B. playsAs
    Indicates that one entity performs, portrays, or assumes the role, character, or persona of another entity.
  • C. playedKeyRoleIn
    Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
  • D. playRoleIn chosen
    Indicates that an entity participates in or performs a specific function, character, or part within an event, context, or system.
  • E. playedEarlyRoleIn
    Indicates that one entity contributed significantly to the initial or formative stages of another entity’s development, success, or emergence.
  • 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_69e25d15db58819092ac1e6791696fd9 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c6dfaae081908be48fa89e625f71 completed April 29, 2026, 8:52 a.m.
PD Predicate disambiguation batch_69f155fe300481909bd617443228df65 completed April 29, 2026, 12:51 a.m.
Created at: April 17, 2026, 7:52 p.m.