Triple

T8335767
Position Surface form Disambiguated ID Type / Status
Subject Harry Potter: Wizards Unite E195781 entity
Predicate allowsPlayerAction P82156 FINISHED
Object join wizarding professions 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: join wizarding professions | Statement: [Harry Potter: Wizards Unite, allowsPlayerAction, join wizarding professions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsPlayerAction
Context triple: [Harry Potter: Wizards Unite, allowsPlayerAction, join wizarding professions]
  • A. canTakeActionWith
    Indicates that one entity is able or permitted to perform an action jointly or in coordination with another entity.
  • B. hasPlayer
    Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
  • C. canBlock
    Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
  • D. hasOpponentAction
    Indicates that one entity performs an action that is in opposition or direct competition to the action of another entity.
  • E. mayActThrough
    Indicates that an entity can exert influence, perform an action, or have an effect by means of another entity, mechanism, or intermediary.
  • F. None of above. chosen

Provenance (4 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd3fc80819097b326119107ad4d completed March 31, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69cb70c3231c81909e3d463192c9de22 completed March 31, 2026, 6:59 a.m.
PDg Predicate description generation batch_69cb76d823b08190a54fadb50660cda5 completed March 31, 2026, 7:25 a.m.
Created at: March 30, 2026, 5:57 p.m.