Triple
T21886430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriot campaigns of 1819 in Venezuela |
E540415
|
entity |
| Predicate | hasMilitaryLeaderSide |
P15490
|
FINISHED |
| Object | Patriot side |
—
|
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: Patriot side | Statement: [Patriot campaigns of 1819 in Venezuela, hasMilitaryLeaderSide, Patriot side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryLeaderSide Context triple: [Patriot campaigns of 1819 in Venezuela, hasMilitaryLeaderSide, Patriot side]
-
A.
notableCommanderSide
Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
-
B.
hasAlliedLeader
Indicates that one entity serves as an allied leader or commander in relation to another entity.
-
C.
notableLeaderSide
Indicates that a person is a prominent or distinguished leader associated with a particular side, faction, or party in a conflict or competition.
-
D.
militaryLeader
chosen
Indicates that one entity serves as the commanding military leader of another entity, such as a state, organization, or armed force.
-
E.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.