Triple
T31389461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Caudine Forks |
E800690
|
entity |
| Predicate | opposingPolity |
P179341
|
FINISHED |
| Object | Samnite League |
—
|
NE NERFINISHED |
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: Samnite League | Statement: [Battle of the Caudine Forks, opposingPolity, Samnite League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposingPolity Context triple: [Battle of the Caudine Forks, opposingPolity, Samnite League]
-
A.
opponentPolities
chosen
Indicates that two polities are in opposition to each other, typically as rivals or enemies in a political, military, or diplomatic context.
-
B.
opposedPoliticalEntity
Indicates that one political entity is in opposition or conflict with another in terms of policies, ideology, or power.
-
C.
opposingPoliticalFaction
Indicates that two entities belong to political groups or factions that are in conflict or opposition to each other.
-
D.
countryOfOpposition
Indicates the country in which an entity faces opposition, resistance, or adversarial activity.
-
E.
oppositionAlliance
Indicates a relationship where entities form or belong to an alliance that is collectively opposed to another entity or group.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 9:19 p.m.