Triple
T24035481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tunis |
E595219
|
entity |
| Predicate | belligerentAllied |
P16682
|
FINISHED |
| Object | British Empire |
—
|
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: British Empire | Statement: [Battle of Tunis, belligerentAllied, British Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belligerentAllied Context triple: [Battle of Tunis, belligerentAllied, British Empire]
-
A.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
-
B.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
C.
belligerentFor
Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
-
D.
alliesInWar
chosen
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d43884819093e9207a99ae2a70 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.