Triple
T31803666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Leo I |
E811809
|
entity |
| Predicate | hasPowerBroker |
P120356
|
FINISHED |
| Object | Aelia Verina |
—
|
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: Aelia Verina | Statement: [court of Leo I, hasPowerBroker, Aelia Verina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerBroker Context triple: [court of Leo I, hasPowerBroker, Aelia Verina]
-
A.
powerBroker
chosen
Indicates a relationship where one entity uses its influence or control to arrange, negotiate, or determine outcomes on behalf of or between other entities.
-
B.
hasPowerBase
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
hasDecisionMakingPower
Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
-
E.
haveFiscalPowers
Indicates that an entity possesses legal authority or control over financial or budgetary matters.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: April 30, 2026, 11:42 p.m.