Triple

T30022237
Position Surface form Disambiguated ID Type / Status
Subject Jan Dodonna E762776 entity
Predicate roleInBattleOfYavin P163790 FINISHED
Object developed attack plan for the Death Star trench run 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: developed attack plan for the Death Star trench run | Statement: [Jan Dodonna, roleInBattleOfYavin, developed attack plan for the Death Star trench run]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattleOfYavin
Context triple: [Jan Dodonna, roleInBattleOfYavin, developed attack plan for the Death Star trench run]
  • A. roleInRogueOne
    Indicates that an entity has a specific acting or production role in the film "Rogue One: A Star Wars Story."
  • B. roleDuringGalacticCivilWar chosen
    Indicates the specific function, position, or involvement an entity had during the Galactic Civil War.
  • C. roleDuringCloneWars
    Indicates the specific function, position, or duties an entity held during the time period of the Clone Wars.
  • D. usesStarfighter
    Indicates that one entity operates or employs a starfighter as its vehicle, tool, or means of transportation or combat.
  • E. roleInGalaxy’sEdge
    Indicates that an entity has a specific role or function within the context of the Galaxy’s Edge setting or environment.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69ff3b32ee148190a3ba3b7600943fef completed May 9, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69ff3a238af88190a2c2245e30299e48 completed May 9, 2026, 1:44 p.m.
Created at: April 29, 2026, 6:47 p.m.