Triple
T36958290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Weapon Dude |
E914242
|
entity |
| Predicate | combatBehavior |
P166029
|
FINISHED |
| Object | stands and fires continuously |
—
|
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: stands and fires continuously | Statement: [Heavy Weapon Dude, combatBehavior, stands and fires continuously]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatBehavior Context triple: [Heavy Weapon Dude, combatBehavior, stands and fires continuously]
-
A.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
B.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
-
C.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
D.
enemyBehavior
chosen
Indicates how an enemy entity acts or responds within a given context, such as its tactics, reactions, or decision patterns toward others.
-
E.
combatRules
Indicates the rules, mechanics, or conditions that govern how combat or fighting interactions are conducted between entities.
- 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.