Triple
T29654956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immortal |
E750239
|
entity |
| Predicate | attackTargets |
P34832
|
FINISHED |
| Object | ground units |
—
|
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 units | Statement: [Immortal, attackTargets, ground units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackTargets Context triple: [Immortal, attackTargets, ground units]
-
A.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
-
B.
attacksIf
Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
-
C.
attacks
chosen
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
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.
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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:54 p.m.