Triple
T36961781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleer Skeleton |
E914324
|
entity |
| Predicate | tacticalThreat |
P50110
|
FINISHED |
| Object | can quickly close distance to player |
—
|
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: can quickly close distance to player | Statement: [Kleer Skeleton, tacticalThreat, can quickly close distance to player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalThreat Context triple: [Kleer Skeleton, tacticalThreat, can quickly close distance to player]
-
A.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made by another entity.
-
B.
targetsThreat
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
-
C.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
D.
tacticalIssue
Indicates a relationship where an entity is involved in, affected by, or characterized as a specific tactical problem, challenge, or concern within an operational context.
-
E.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.