Triple
T31762945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synod of Rome (963) |
E810728
|
entity |
| Predicate | hasImperialBacker |
P10151
|
FINISHED |
| Object | Otto I, Holy Roman Emperor |
—
|
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: Otto I, Holy Roman Emperor | Statement: [Synod of Rome (963), hasImperialBacker, Otto I, Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImperialBacker Context triple: [Synod of Rome (963), hasImperialBacker, Otto I, Holy Roman Emperor]
-
A.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
-
B.
backedFor
Indicates that one entity provides support, endorsement, or backing for another entity, often in a financial, political, or strategic context.
-
C.
hadImperialStatus
Indicates that an entity possessed or was granted imperial rank, authority, or official status within an empire.
-
D.
hasSupporter
chosen
Indicates that one entity supports, endorses, or backs another entity.
-
E.
canBeBackedBy
Indicates that one entity is capable of being supported, guaranteed, or secured by 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_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 30, 2026, 11:31 p.m.