Triple

T23363784
Position Surface form Disambiguated ID Type / Status
Subject Gondwana Station E593254 entity
Predicate hasLogisticalRole P152431 FINISHED
Object support for German Antarctic expeditions 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: support for German Antarctic expeditions | Statement: [Gondwana Station, hasLogisticalRole, support for German Antarctic expeditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLogisticalRole
Context triple: [Gondwana Station, hasLogisticalRole, support for German Antarctic expeditions]
  • A. hasCargoRole
    Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
  • B. hasShipRole
    Indicates that an entity holds or is assigned a specific role or function on a ship.
  • C. logisticalCharacteristic
    Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
  • D. logisticsSupportFrom
    Indicates that one entity provides logistical assistance, resources, or services to another entity.
  • E. roleInvolves
    Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
  • 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aac4248190a4663ed12aed6856 completed April 29, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69f061c7aaa48190a58ce93f87155ffc completed April 28, 2026, 7:29 a.m.
PDg Predicate description generation batch_69f0bd4a0e408190ad8916faf23562d9 completed April 28, 2026, 1:59 p.m.
Created at: April 17, 2026, 5:31 p.m.