Triple
T31118305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Phocas |
E793151
|
entity |
| Predicate | riseToPowerMethod |
P4209
|
FINISHED |
| Object | military coup |
—
|
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: military coup | Statement: [House of Phocas, riseToPowerMethod, military coup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riseToPowerMethod Context triple: [House of Phocas, riseToPowerMethod, military coup]
-
A.
methodOfGainingPower
Indicates the way or process through which an entity acquires or increases power.
-
B.
cameToPowerThrough
chosen
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
C.
roseToPowerIn
Indicates the point in time or context in which an entity gained authority, control, or a dominant position.
-
D.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
E.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.