Triple
T28774259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Mongus |
E726491
|
entity |
| Predicate | empireContext |
P165574
|
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: [Peter Mongus, empireContext, Eastern Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: empireContext Context triple: [Peter Mongus, empireContext, Eastern Roman Empire]
-
A.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
B.
dynastyContext
Indicates the historical or cultural dynasty within which an entity, event, or relationship is situated or contextualized.
-
C.
historicalEmpireCenter
Indicates that a location served as the primary political or administrative center of a historical empire.
-
D.
successorEmpireContext
Indicates that one empire is the historical or political successor to another within a specific contextual framework (such as time period, region, or lineage).
-
E.
monarchicContext
Indicates that the relationship or action occurs within, is shaped by, or pertains to a monarchical system of rule or authority.
- 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_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:17 a.m.