Triple

T15280936
Position Surface form Disambiguated ID Type / Status
Subject Second Kamchatka Expedition E365266 entity
Predicate subEvent P6285 FINISHED
Object Bering’s voyage to Alaska in 1741 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: Bering’s voyage to Alaska in 1741 | Statement: [Second Kamchatka Expedition, subEvent, Bering’s voyage to Alaska in 1741]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subEvent
Context triple: [Second Kamchatka Expedition, subEvent, Bering’s voyage to Alaska in 1741]
  • A. alternativeEvent
    Indicates that one event serves as an alternative or substitute option to another event within the same context.
  • B. hasSubEvent chosen
    Indicates that an event is composed of, or includes as part of its structure, another event that occurs within it.
  • C. parentEvent
    Indicates that one event serves as the higher-level or originating event from which another event is derived, contained, or logically dependent.
  • D. subtheme
    Indicates that one topic or concept functions as a more specific, subordinate theme within a broader overarching theme.
  • E. mainEventFor
    Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
  • 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_69d85a103d9081908c1ea6c4c73ac8e3 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00e504d8c8190ad6c565a31d1a9bd completed April 15, 2026, 10:16 p.m.
PD Predicate disambiguation batch_69deca90739081909bd1b797cdb8af2b completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:15 a.m.