Triple

T8268585
Position Surface form Disambiguated ID Type / Status
Subject Expedition Robinson E193361 entity
Predicate usesEliminationProcess P42993 FINISHED
Object yes 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: yes | Statement: [Expedition Robinson, usesEliminationProcess, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesEliminationProcess
Context triple: [Expedition Robinson, usesEliminationProcess, yes]
  • A. usesEliminationMethod chosen
    Indicates that one entity applies an elimination-based method or process to solve, simplify, or remove elements in relation to another entity or problem.
  • B. hasEliminationRoute
    Indicates that there exists a specific pathway or method by which something can be removed, discharged, or otherwise eliminated from a system or context.
  • C. usedProcess
    Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
  • D. isEliminatedPrimarilyBy
    Indicates that one entity serves as the main means or pathway by which another entity is removed, cleared, or disposed of.
  • E. loserElimination
    Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
  • 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_69ca82e081d48190986beaa51f498ab9 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb795127ac81908196008f5579f83f completed March 31, 2026, 7:35 a.m.
PD Predicate disambiguation batch_69cb70a4525481909399d313a6247ace completed March 31, 2026, 6:58 a.m.
Created at: March 30, 2026, 5:50 p.m.