Triple
T29786753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asante |
E756284
|
entity |
| Predicate | historicalMilitaryPower |
P105554
|
FINISHED |
| Object | Ashanti 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: Ashanti Empire | Statement: [Asante, historicalMilitaryPower, Ashanti Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMilitaryPower Context triple: [Asante, historicalMilitaryPower, Ashanti Empire]
-
A.
historicalPower
Indicates that one entity held significant influence, control, or authority over another during a past period.
-
B.
historicalFaction
Indicates that an entity was a member of, associated with, or part of a particular faction or side in a historical context or conflict.
-
C.
politicalEntityHistorically
Indicates that a political entity held a particular status, role, or relationship during a past historical period, but not necessarily in the present.
-
D.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
E.
militaryHistoryTopic
chosen
Indicates that there exists a relationship where the subject is a topic, theme, or subject matter specifically concerned with military history.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: April 29, 2026, 5:09 p.m.