Triple
T29050422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgardian Royal Family |
E735249
|
entity |
| Predicate | primaryWeaponAssociated |
P6066
|
FINISHED |
| Object | Mjolnir |
—
|
NE NERFINISHED |
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: Mjolnir | Statement: [Asgardian Royal Family, primaryWeaponAssociated, Mjolnir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWeaponAssociated Context triple: [Asgardian Royal Family, primaryWeaponAssociated, Mjolnir]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
primaryArmament
chosen
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
weaponSystemAssociatedWith
Indicates that one entity is functionally or organizationally connected to a particular weapon system, such as by using, supporting, or being part of that system.
-
D.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
E.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: April 28, 2026, 10:08 a.m.