Triple
T28773994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspar |
E726484
|
entity |
| Predicate | dominatedPoliticsIn |
P176726
|
FINISHED |
| Object | Eastern Roman 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: Eastern Roman Empire | Statement: [Aspar, dominatedPoliticsIn, Eastern Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominatedPoliticsIn Context triple: [Aspar, dominatedPoliticsIn, Eastern Roman Empire]
-
A.
politicallyIn
Indicates that one entity is located within, belongs to, or falls under the political jurisdiction or authority of another entity.
-
B.
socioPoliticalDomainOf
Indicates the socio-political sphere, context, or domain within which an entity, action, or relationship is situated or exerts influence.
-
C.
partyDominance
Indicates that one political party holds a prevailing or controlling position over others within a given political context or system.
-
D.
dominantPoliticalMovement
Indicates that one political movement holds primary influence or control over the political landscape in a given context.
-
E.
politicalCategory
Indicates the political classification or ideological grouping that an entity belongs to or is associated with.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 6:17 a.m.