Triple
T34353828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Saxe-Eisenberg |
E881657
|
entity |
| Predicate | rulingFamilyReligion |
P21571
|
FINISHED |
| Object | Lutheran |
—
|
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: Lutheran | Statement: [Duchy of Saxe-Eisenberg, rulingFamilyReligion, Lutheran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingFamilyReligion Context triple: [Duchy of Saxe-Eisenberg, rulingFamilyReligion, Lutheran]
-
A.
religionOfMonarch
Indicates the religious affiliation or faith practiced by a given monarch.
-
B.
hasPrimaryReligionOfRulers
Indicates that the specified religion is the main or official faith practiced or endorsed by the rulers of an entity.
-
C.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
D.
dynasticReligion
chosen
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
E.
religiousRoleOfRuler
Indicates that a ruler holds a specific religious office, function, or authority within a religious system or tradition.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.