Triple
T28718663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Social War |
E730029
|
entity |
| Predicate | opponentCollective |
P116577
|
FINISHED |
| Object | Marsic Confederation |
—
|
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: Marsic Confederation | Statement: [Roman Social War, opponentCollective, Marsic Confederation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentCollective Context triple: [Roman Social War, opponentCollective, Marsic Confederation]
-
A.
opponentGroup
chosen
Indicates that one group is in opposition or conflict with another group, typically as a rival, competitor, or adversary.
-
B.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
C.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
D.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
-
E.
opponentInScenario
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 5:52 a.m.