Triple
T37554282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azuresong Mageblade |
E933656
|
entity |
| Predicate | weaponSubClass |
P16410
|
FINISHED |
| Object | one-handed sword |
—
|
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: one-handed sword | Statement: [Azuresong Mageblade, weaponSubClass, one-handed sword]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponSubClass Context triple: [Azuresong Mageblade, weaponSubClass, one-handed sword]
-
A.
weaponCategory
chosen
Indicates the classification or type of weapon to which an item or armament belongs.
-
B.
weaponFamily
Indicates that two weapons belong to the same broader classification or type group based on shared characteristics or lineage.
-
C.
secondaryWeaponTechnology
Indicates that one entity serves as a secondary or backup weapon system or technology associated with another entity.
-
D.
limitedWeaponType
Indicates that the use or availability of a weapon is restricted to a specific type or set of types.
-
E.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.