Triple

T16191101
Position Surface form Disambiguated ID Type / Status
Subject The Phantom E392940 entity
Predicate hasAllegianceInStory P47185 FINISHED
Object fictional Palestinian militant group 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: fictional Palestinian militant group | Statement: [The Phantom, hasAllegianceInStory, fictional Palestinian militant group]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAllegianceInStory
Context triple: [The Phantom, hasAllegianceInStory, fictional Palestinian militant group]
  • A. hadAllegiance
    Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
  • B. hasAllyInStory
    Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
  • C. protagonistAllegiance chosen
    Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
  • D. allegianceArc
    Indicates a change or evolution in an entity’s loyalty or allegiance to another entity over time.
  • E. stateAllegiance
    Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
  • 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_69d87f1e49ac8190a311b54d32990576 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e222d5769c8190bbb604bfa095a1a5 completed April 17, 2026, 12:08 p.m.
PD Predicate disambiguation batch_69e219e11f6081909106b1240a17fd37 completed April 17, 2026, 11:30 a.m.
Created at: April 10, 2026, 5:02 a.m.