Triple
T31762527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Antioch (272) |
E810719
|
entity |
| Predicate | romanEmperorInvolved |
P27872
|
FINISHED |
| Object | Aurelian |
—
|
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: Aurelian | Statement: [Siege of Antioch (272), romanEmperorInvolved, Aurelian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanEmperorInvolved Context triple: [Siege of Antioch (272), romanEmperorInvolved, Aurelian]
-
A.
underRomanEmperor
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
B.
associatedWithEmperor
chosen
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
C.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
D.
ByzantineEmperorDuringConflict
Indicates that a person held the office of Byzantine Emperor during the time span of a specified conflict.
-
E.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 11:31 p.m.