Triple
T4737273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles, Lord Goring |
E105154
|
entity |
| Predicate | foughtForSide |
P375
|
FINISHED |
| Object | Royalist side in the English Civil War |
—
|
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: Royalist side in the English Civil War | Statement: [Charles, Lord Goring, foughtForSide, Royalist side in the English Civil War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtForSide Context triple: [Charles, Lord Goring, foughtForSide, Royalist side in the English Civil War]
-
A.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
C.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
D.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
-
E.
countryOfVictoriousSide
Indicates the country to which the winning or victorious side in a conflict, competition, or contest belongs.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64844b7081909c9d36e4b461379e |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.