Triple

T881720
Position Surface form Disambiguated ID Type / Status
Subject Santiago (Magellan expedition ship) E19039 entity
Predicate crewOutcome P20707 FINISHED
Object crew largely survived the loss of the ship 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: crew largely survived the loss of the ship | Statement: [Santiago (Magellan expedition ship), crewOutcome, crew largely survived the loss of the ship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: crewOutcome
Context triple: [Santiago (Magellan expedition ship), crewOutcome, crew largely survived the loss of the ship]
  • A. crewModule
    Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
  • B. crew
    Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
  • C. missionAccident
    Indicates that an accident or unintended harmful event occurred during the course of a mission or operation.
  • D. missionFailure
    Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
  • E. intendedCrewVehicle
    Indicates that a particular vehicle is designated or planned to be used by a specific crew.
  • F. None of above. chosen

Provenance (4 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_69a4939c32488190a7ccd41cf0abb22b completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4accc863c8190be9e5350732c30b1 completed March 1, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69a4aa8eca748190b58e0f08b30fba43 completed March 1, 2026, 9:07 p.m.
PDg Predicate description generation batch_69a4ab4a38ec8190915916d80299ab55 completed March 1, 2026, 9:10 p.m.
Created at: March 1, 2026, 7:39 p.m.