Triple
T9594975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SK-105 Kürassier |
E231507
|
entity |
| Predicate | intendedOpponents |
P89124
|
FINISHED |
| Object | enemy main battle tanks |
—
|
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: enemy main battle tanks | Statement: [SK-105 Kürassier, intendedOpponents, enemy main battle tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOpponents Context triple: [SK-105 Kürassier, intendedOpponents, enemy main battle tanks]
-
A.
invitedOpponents
Indicates that one entity extended an invitation to another entity specifically in the context of being opponents, such as in a match, contest, or competitive event.
-
B.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
C.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
D.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
E.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
- F. None of above. chosen
Provenance (4 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a14fd308190beb8fda5a9e912c7 |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.