Triple
T21334850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Saxe-Wittenberg |
E526013
|
entity |
| Predicate | hadImperialStatus |
P143768
|
FINISHED |
| Object | prince-electorate-designate of the Holy Roman Empire |
—
|
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: prince-electorate-designate of the Holy Roman Empire | Statement: [Duchy of Saxe-Wittenberg, hadImperialStatus, prince-electorate-designate of the Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadImperialStatus Context triple: [Duchy of Saxe-Wittenberg, hadImperialStatus, prince-electorate-designate of the Holy Roman Empire]
-
A.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
B.
hadImperialCircle
Indicates that an entity was administratively organized within a specific Imperial Circle of the Holy Roman Empire.
-
C.
hadMemberInImperialFamily
Indicates that an entity had at least one member belonging to an imperial family.
-
D.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
E.
reachedRoyalStatusInCentury
Indicates that an entity attained royal status or became recognized as royalty during a specified century.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e898d602c08190821c63e0aff42fc2 |
completed | April 22, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:43 p.m.