Triple

T23740910
Position Surface form Disambiguated ID Type / Status
Subject Plan B (Interstellar) E586667 entity
Predicate actualIntendedPriority P25884 FINISHED
Object primary plan for human survival 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: primary plan for human survival | Statement: [Plan B (Interstellar), actualIntendedPriority, primary plan for human survival]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: actualIntendedPriority
Context triple: [Plan B (Interstellar), actualIntendedPriority, primary plan for human survival]
  • A. planningPriority
    Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
  • B. priorityDeterminedBy
    Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
  • C. originalIntendedStatus
    Indicates the status that was initially planned or expected for an entity before any changes or updates occurred.
  • D. typeOfPriority chosen
    Indicates the specific priority level or category assigned to something relative to other items or tasks.
  • E. limitsPriorityOf
    Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
  • 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_69e24908efb08190bf755c3a9b91f222 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bad61d908190a0a8493bbba95d49 completed April 29, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69f155f012808190a4b1cbc155558ade completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 7:11 p.m.