Triple
T20512780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yao’s next-bit test |
E503604
|
entity |
| Predicate | adversaryGoal |
P38945
|
FINISHED |
| Object | predict the next output bit |
—
|
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: predict the next output bit | Statement: [Yao’s next-bit test, adversaryGoal, predict the next output bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adversaryGoal Context triple: [Yao’s next-bit test, adversaryGoal, predict the next output bit]
-
A.
aimOfAttacker
chosen
Indicates that a particular goal, target, or objective is what the attacker intends to achieve or affect.
-
B.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
-
C.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
D.
primaryAdversaryPlanning
Indicates that an entity is the main opposing force actively formulating or directing plans against another entity.
-
E.
objectiveOfAttackers
Indicates the target or goal that attackers aim to reach or affect through their attack.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dcd74c48190b050e25c20154c09 |
completed | April 20, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.