Triple
T35231783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohemian electoral dignity |
E1017255
|
entity |
| Predicate | originalElectorsListedIn |
P106578
|
FINISHED |
| Object | Golden Bull of 1356 |
E50992
|
NE 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: Golden Bull of 1356 | Statement: [Bohemian electoral dignity, originalElectorsListedIn, Golden Bull of 1356]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalElectorsListedIn Context triple: [Bohemian electoral dignity, originalElectorsListedIn, Golden Bull of 1356]
-
A.
numberOfElectors
Indicates the total count of electors associated with a given entity or context.
-
B.
electoralList
chosen
Indicates that an entity is part of, or associated with, a specific electoral list used in an election.
-
C.
hasElectorsFrom
Indicates that an entity possesses or is associated with electors originating from a specified source or group.
-
D.
hasElectors
Indicates that an entity is associated with one or more electors who have the authority to vote or make a selection on its behalf.
-
E.
previousElectorate
Indicates that one electorate served as the earlier or former electoral district associated with another electorate.
- F. None of above.
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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819d027988190b9236a1405f32483 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.