Triple
T37462833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tar Creeper |
E930960
|
entity |
| Predicate | attackOnOpponentTurn |
P189401
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Tar Creeper, attackOnOpponentTurn, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackOnOpponentTurn Context triple: [Tar Creeper, attackOnOpponentTurn, 3]
-
A.
attackOnYourTurn
Indicates that the action of attacking occurs during the subject’s own turn in the sequence of play or events.
-
B.
canAttackOnOpponentsTurn
chosen
Indicates that an entity is able to perform an attack during the opposing side’s turn rather than only on its own turn.
-
C.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
D.
forceAttacked
Indicates that one entity carried out an attack against another entity using force or coercive power.
-
E.
aidedOpponent
Indicates that one entity provided help or support to another entity who is considered an opponent or adversary.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.