Triple
T38593779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Arrow |
E932514
|
entity |
| Predicate | isFiredAs |
P58412
|
FINISHED |
| Object | arrow projectile |
—
|
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: arrow projectile | Statement: [Sonic Arrow, isFiredAs, arrow projectile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFiredAs Context triple: [Sonic Arrow, isFiredAs, arrow projectile]
-
A.
firedBy
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
B.
canBeFiredIn
Indicates that an entity (such as a weapon or device) is capable of being discharged or operated within a specified medium, environment, or container.
-
C.
triggeredFires
Indicates that one entity caused or initiated the occurrence of one or more fires in another entity or location.
-
D.
isFireFollower
Indicates that an entity follows, worships, or is devoted to fire or a fire-related power or doctrine.
-
E.
designedToFire
chosen
Indicates that one entity is intended or configured to discharge, launch, or emit another entity (such as a projectile, signal, or event).
- 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_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.