Triple

T29082807
Position Surface form Disambiguated ID Type / Status
Subject Star-Lord (Marvel Cinematic Universe) E734022 entity
Predicate roleInBattle of Earth P28183 FINISHED
Object key hero in final stand against Thanos 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: key hero in final stand against Thanos | Statement: [Star-Lord (Marvel Cinematic Universe), roleInBattle of Earth, key hero in final stand against Thanos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInBattle of Earth
Context triple: [Star-Lord (Marvel Cinematic Universe), roleInBattle of Earth, key hero in final stand against Thanos]
  • A. roleInElysium
    Indicates that an entity holds a specific role, position, or function within the context of Elysium.
  • B. roleInAlienCovenant
    Indicates that an entity has a role or participation in the film "Alien: Covenant."
  • C. roleInWarOrConflict
    Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
  • D. roleAtThePlanet
    Indicates that an entity holds or performs a specific role or function at, on, or for a particular planet.
  • E. notableBattleRole chosen
    Indicates the specific role or function an entity played in a notable or historically significant battle.
  • 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_69f05b0c0f28819086eae6e84f2ae472 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69fec5c503808190bde0b1829ea43071 completed May 9, 2026, 5:27 a.m.
PD Predicate disambiguation batch_69fec535dd6c8190a6ab85201f5a04a9 completed May 9, 2026, 5:25 a.m.
Created at: April 28, 2026, 10:57 a.m.