Triple
T22448667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean Sea theater |
E554929
|
entity |
| Predicate | primaryBelligerents |
P137647
|
FINISHED |
| Object | European colonial powers |
—
|
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: European colonial powers | Statement: [Caribbean Sea theater, primaryBelligerents, European colonial powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBelligerents Context triple: [Caribbean Sea theater, primaryBelligerents, European colonial powers]
-
A.
majorBelligerent
chosen
Indicates that an entity is a primary or principal participant in a conflict, war, or large-scale hostile engagement.
-
B.
countryAtWarWith
Indicates that two countries are engaged in an active state of war or armed conflict with each other.
-
C.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
D.
battlesWith
Indicates that two entities are engaged in active conflict, combat, or struggle against each other.
-
E.
endedBilateralWarBetween
Indicates that an action or event brought a bilateral war between two parties to a conclusion or cessation.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4a20f8819097f471084e97e099 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.