Triple
T1673688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-British National Liberation War |
E36181
|
entity |
| Predicate | hasOpposingForceType |
P31619
|
FINISHED |
| Object | colonial power |
—
|
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: colonial power | Statement: [Anti-British National Liberation War, hasOpposingForceType, colonial power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpposingForceType Context triple: [Anti-British National Liberation War, hasOpposingForceType, colonial power]
-
A.
hasOpposingFront
Indicates that one entity’s front side is directly facing or oriented opposite to the front side of another entity.
-
B.
hasOpposingAlliance
Indicates that two entities belong to alliances or factions that are in direct opposition or conflict with each other.
-
C.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
-
D.
opposingForcesStatus
Indicates the current state or condition of two or more forces that are in conflict or opposition to each other.
-
E.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
- F. None of above. chosen
Provenance (4 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab271be3f4819091adcd745dec8159 |
completed | March 6, 2026, 7:12 p.m. |
Created at: March 4, 2026, 7:29 p.m.