Triple
T38593591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fan of Blades |
E932509
|
entity |
| Predicate | firesProjectilesPerUse |
P191274
|
FINISHED |
| Object | three shuriken |
—
|
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: three shuriken | Statement: [Fan of Blades, firesProjectilesPerUse, three shuriken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firesProjectilesPerUse Context triple: [Fan of Blades, firesProjectilesPerUse, three shuriken]
-
A.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
-
B.
ammoConsumptionPerUse
chosen
Indicates the amount of ammunition that is used up each time the associated action or item is used.
-
C.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
D.
numberOfShotsFired
Indicates the total count of shots that were discharged in the described event or action.
-
E.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.