Triple

T12852410
Position Surface form Disambiguated ID Type / Status
Subject 2018 Kerch Strait incident E307356 entity
Predicate numberOfUkrainianSailorsDetained P14018 FINISHED
Object 24 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: 24 | Statement: [2018 Kerch Strait incident, numberOfUkrainianSailorsDetained, 24]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfUkrainianSailorsDetained
Context triple: [2018 Kerch Strait incident, numberOfUkrainianSailorsDetained, 24]
  • A. detainedPrisonersFrom
    Indicates that an authority is holding prisoners who originate from or are associated with a specified place or source.
  • B. detainedBy
    Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
  • C. estimatedPrisonerCount chosen
    Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
  • D. estimatedPrisoners
    Indicates a relationship where a value represents the estimated number of prisoners associated with a particular entity or context.
  • E. detainedFor
    Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9714208f881908f7f8a921362909a completed April 10, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69d96fa3002881908000357b1f95a3ac completed April 10, 2026, 9:46 p.m.
Created at: April 9, 2026, 5:36 p.m.