Triple
T11478141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Peonnum |
E272074
|
entity |
| Predicate | possibleOpponent |
P48619
|
FINISHED |
| Object | neighboring Britons |
—
|
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: neighboring Britons | Statement: [Battle of Peonnum, possibleOpponent, neighboring Britons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOpponent Context triple: [Battle of Peonnum, possibleOpponent, neighboring Britons]
-
A.
aidedOpponent
Indicates that one entity provided help or support to another entity who is considered an opponent or adversary.
-
B.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
C.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
D.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
-
E.
consideredOpponentsAs
chosen
Indicates that one entity regarded or treated another entity as 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294e0fe08190b018e840146e27ca |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.