Triple
T29655053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Void Ray |
E750241
|
entity |
| Predicate | attackTargetType |
P168669
|
FINISHED |
| Object | ground |
—
|
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 | Statement: [Void Ray, attackTargetType, ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTargetType Context triple: [Void Ray, attackTargetType, ground]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made by another entity.
-
C.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
D.
aimOfAttacker
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
E.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
- F. None of above. chosen
Provenance (4 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 6:54 p.m.