Triple
T35394371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snifit |
E1023029
|
entity |
| Predicate | typicalAttack |
P4333
|
FINISHED |
| Object | shooting projectiles in a straight line |
—
|
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: shooting projectiles in a straight line | Statement: [Snifit, typicalAttack, shooting projectiles in a straight line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAttack Context triple: [Snifit, typicalAttack, shooting projectiles in a straight line]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackValue
Indicates the offensive strength or damage potential an entity can inflict in an interaction or combat scenario.
-
C.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
D.
attackName
Indicates the specific name or designation given to an attack action or offensive maneuver.
-
E.
attackOnYourTurn
Indicates that the action of attacking occurs during the subject’s own turn in the sequence of play or events.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.