Triple
T31103386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MUTO |
E792732
|
entity |
| Predicate | primaryAdversaryIn |
P4675
|
FINISHED |
| Object | Battle of San Francisco |
E1884708
|
NE 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: Battle of San Francisco | Statement: [MUTO, primaryAdversaryIn, Battle of San Francisco]
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 (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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2938ad4b788190831c40f7cac8644f |
completed | June 10, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:03 p.m.