Triple
T26084301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formidable |
E657936
|
entity |
| Predicate | belligerentAfterCapture |
P76698
|
FINISHED |
| Object | United Kingdom |
—
|
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 Kingdom | Statement: [Formidable, belligerentAfterCapture, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentAfterCapture Context triple: [Formidable, belligerentAfterCapture, United Kingdom]
-
A.
belligerentSideAfterCapture
chosen
Indicates the party or side that an entity belongs to after it has been captured in a conflict or competitive interaction.
-
B.
belligerentFor
Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
-
C.
belligerentControl
Indicates that one party exercises control, authority, or coercive influence over another in a hostile or conflict-oriented context.
-
D.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
E.
coBelligerent
Indicates that two or more parties are engaged in hostilities against a common enemy, typically as allies or coordinated participants in the same conflict.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606fd78188190a73f149ce8e176a1 |
completed | May 2, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:41 p.m.