Triple
T31103386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUTO |
E792732
|
entity |
| Predicate | primaryAdversaryIn |
—
|
GENERATED |
| Object | Battle of San Francisco |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAdversaryIn Context triple: [MUTO, primaryAdversaryIn, Battle of San Francisco]
-
A.
primaryAdversaryImplied
Indicates that an entity is understood or suggested, rather than explicitly stated, to be the main opponent or chief adversary of another entity.
-
B.
primaryAdversaryContext
Indicates the main opposing force or conflict-driving element that defines the central adversarial situation within a given context.
-
C.
primaryAdversaryDirection
Indicates the direction from an entity toward its main or most significant adversary.
-
D.
primaryEnemy
chosen
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
E.
primaryAntagonists
Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
- F. None of above.
Provenance (1 batch)
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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:03 p.m.