Triple
T37511286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sound Barrier |
E932522
|
entity |
| Predicate | counterplayTo |
P100355
|
FINISHED |
| Object | high burst damage |
—
|
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: high burst damage | Statement: [Sound Barrier, counterplayTo, high burst damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: counterplayTo Context triple: [Sound Barrier, counterplayTo, high burst damage]
-
A.
counterplay
chosen
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
B.
counterMeasureAgainst
Indicates a relationship where one entity serves as a response or defensive action intended to prevent, mitigate, or neutralize the effects of another entity.
-
C.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
D.
counterCountermeasures
Indicates actions or strategies specifically designed to neutralize, defeat, or bypass existing countermeasures.
-
E.
counterSlogan
Indicates that one slogan is created or used specifically to oppose, refute, or undermine another slogan.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.