Triple

T34698890
Position Surface form Disambiguated ID Type / Status
Subject SS Empress of Britain (1905) E1000305 entity
Predicate builtForService P8196 FINISHED
Object North Atlantic 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: North Atlantic | Statement: [SS Empress of Britain (1905), builtForService, North Atlantic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: builtForService
Context triple: [SS Empress of Britain (1905), builtForService, North Atlantic]
  • A. structureBuiltFor
    Indicates that one entity was constructed specifically to serve, house, or support the function, use, or needs of another entity.
  • B. isBuiltFor chosen
    Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
  • C. usedForService
    Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
  • D. isAlsoBuiltFor
    Indicates that something is additionally designed or constructed to serve another purpose, use, or type of entity beyond its primary one.
  • E. isForService
    Indicates that something is intended, designated, or used to provide a particular service or function for someone or something.
  • 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_69f76dab937881909c86f1b9ad50445f completed May 3, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7805ce6208190ac6dbd9c97989978 completed May 3, 2026, 5:05 p.m.
PD Predicate disambiguation batch_69f77956ec648190ba4fb7e9d83fd107 completed May 3, 2026, 4:35 p.m.
Created at: May 3, 2026, 3:59 p.m.