Triple

T30036692
Position Surface form Disambiguated ID Type / Status
Subject The Sea Chase E763177 entity
Predicate featuresFictionalVessel P69373 FINISHED
Object German freighter Ergenstrasse NE NERFINISHED

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: German freighter Ergenstrasse | Statement: [The Sea Chase, featuresFictionalVessel, German freighter Ergenstrasse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuresFictionalVessel
Context triple: [The Sea Chase, featuresFictionalVessel, German freighter Ergenstrasse]
  • A. featuresVessel
    Indicates that one entity includes, presents, or prominently displays a particular vessel as part of its composition, content, or configuration.
  • B. fictionalShip chosen
    Indicates that one entity is a ship that exists only in fiction or narrative works, rather than in reality.
  • C. featuresFictionalUnit
    Indicates that something includes or presents a fictional unit (such as a character, group, or organization) as part of its content or structure.
  • D. navalFeatures
    Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
  • E. notableShip
    Indicates that there is a notable or significant ship associated with the subject entity.
  • 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_69f2246fb2b88190acff36bf7975c8f0 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69ffc083a54c8190ac80d05ee8d20a6b completed May 9, 2026, 11:17 p.m.
PD Predicate disambiguation batch_69ffbfeb05b88190b4d50ce8124004d9 completed May 9, 2026, 11:14 p.m.
Created at: April 29, 2026, 6:51 p.m.