Triple
T37456855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spore Crawler |
E930820
|
entity |
| Predicate | targetableBy |
P143292
|
FINISHED |
| Object | ground attacks |
—
|
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: ground attacks | Statement: [Spore Crawler, targetableBy, ground attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetableBy Context triple: [Spore Crawler, targetableBy, ground attacks]
-
A.
canTarget
chosen
Indicates that one entity is able or permitted to select, aim at, or direct its action or effect toward another entity as a target.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
D.
targetRole
Indicates the specific role or function that an entity is intended or designated to fulfill in a given context.
-
E.
cannotTarget
Indicates that one entity is unable or not permitted to select or act upon another entity as a target.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:17 p.m.