Triple
T33613345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Saxe-Altenburg |
E861046
|
entity |
| Predicate | heldTitleWithin |
P176958
|
FINISHED |
| Object | Holy 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: Holy Roman Empire | Statement: [Dukes of Saxe-Altenburg, heldTitleWithin, Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleWithin Context triple: [Dukes of Saxe-Altenburg, heldTitleWithin, Holy Roman Empire]
-
A.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
B.
heldTitleAlongWith
Indicates that two or more entities simultaneously held the same title or position during an overlapping period.
-
C.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
D.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in time.
-
E.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:41 a.m.