Triple
T14788810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denkyira |
E347597
|
entity |
| Predicate | statusAfterDefeat |
P109227
|
FINISHED |
| Object | subordinate state within the Ashanti Empire |
—
|
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: subordinate state within the Ashanti Empire | Statement: [Denkyira, statusAfterDefeat, subordinate state within the Ashanti Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterDefeat Context triple: [Denkyira, statusAfterDefeat, subordinate state within the Ashanti Empire]
-
A.
afterDefeat
Indicates that one event, state, or action occurs subsequent to and as a consequence of a defeat of some party or entity.
-
B.
treatmentAfterDefeat
Indicates that one entity’s treatment of another occurs subsequent to that other entity’s defeat.
-
C.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
D.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
E.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.