Triple
T35357305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Lady Prevost |
E1021368
|
entity |
| Predicate | laterBelligerentSide |
P375
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [HMS Lady Prevost, laterBelligerentSide, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBelligerentSide Context triple: [HMS Lady Prevost, laterBelligerentSide, United States]
-
A.
secondaryBelligerent
Indicates that an entity participates in a conflict as a secondary or supporting belligerent rather than as a primary combatant.
-
B.
belligerentSideLeavingWar
Indicates that a party involved in an armed conflict ceases participation and withdraws from the war.
-
C.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
belligerentSideRemainingOpposite
Indicates that the referenced side is the remaining opposing party in a conflict or dispute after other belligerent sides have been removed or resolved.
-
E.
belligerentSupport
Indicates support given to a party engaged in conflict or hostilities, often implying backing one side in a belligerent or warlike 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 3, 2026, 4:03 p.m.