Triple

T28674246
Position Surface form Disambiguated ID Type / Status
Subject June Branch E725815 entity
Predicate powerSourceOfWeapon P168586 FINISHED
Object Norse magic (implied origin of axe) 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: Norse magic (implied origin of axe) | Statement: [June Branch, powerSourceOfWeapon, Norse magic (implied origin of axe)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: powerSourceOfWeapon
Context triple: [June Branch, powerSourceOfWeapon, Norse magic (implied origin of axe)]
  • A. hasEnergyWeapons
    Indicates that an entity is equipped with or uses weapons that emit or manipulate energy (such as lasers or plasma) rather than conventional physical projectiles.
  • B. primaryArmament
    Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
  • C. weaponCapability
    Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
  • D. weapon
    Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
  • E. powerHarnessedBy chosen
    Indicates that a source of power or energy is captured, controlled, or utilized by a particular agent or system.
  • 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_69f01d867608819086bc3e6b4f9de866 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f6b903538481909cffcb6cc1cc0e70 completed May 3, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69f6b626120c819097c9ad04487570d7 completed May 3, 2026, 2:42 a.m.
Created at: April 28, 2026, 5:05 a.m.