Triple
T28774003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspar |
E726484
|
entity |
| Predicate | couldNotBecomeEmperorBecauseOf |
P49485
|
FINISHED |
| Object | Arian faith |
—
|
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: Arian faith | Statement: [Aspar, couldNotBecomeEmperorBecauseOf, Arian faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldNotBecomeEmperorBecauseOf Context triple: [Aspar, couldNotBecomeEmperorBecauseOf, Arian faith]
-
A.
reasonForNotBecomingKing
chosen
Indicates the circumstance, cause, or justification that prevented someone from becoming king.
-
B.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
C.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
D.
formedUnderEmperor
Indicates that an entity (such as a group, institution, or administrative unit) was created or established during the reign or authority of a specific emperor.
-
E.
hasNotableEmperor
Indicates that an entity is associated with at least one emperor who is historically recognized as particularly important or distinguished.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:17 a.m.