Triple
T35808796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKO |
E1035172
|
entity |
| Predicate | canBeCounteredInto |
P100355
|
FINISHED |
| Object | mid-air variation |
—
|
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: mid-air variation | Statement: [RKO, canBeCounteredInto, mid-air variation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCounteredInto Context triple: [RKO, canBeCounteredInto, mid-air variation]
-
A.
primaryAdversaryCapabilityCountered
Indicates that a primary adversary capability is neutralized, mitigated, or otherwise rendered ineffective by a specified countermeasure or action.
-
B.
counterplay
chosen
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
C.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
-
D.
canBeChallengedOn
Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
-
E.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 3, 2026, 4:06 p.m.