Triple
T461857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles IV, Holy Roman Emperor |
E7355
|
entity |
| Predicate | reignAsKingOfBohemiaStart |
P1506
|
FINISHED |
| Object | 1346 |
—
|
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: 1346 | Statement: [Charles IV, Holy Roman Emperor, reignAsKingOfBohemiaStart, 1346]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsKingOfBohemiaStart Context triple: [Charles IV, Holy Roman Emperor, reignAsKingOfBohemiaStart, 1346]
-
A.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
B.
successorAsHolyRomanEmperor
Indicates that one entity directly follows another in holding the title of Holy Roman Emperor.
-
C.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
D.
reasonForStartOfReign
Indicates the cause, circumstance, or event that led to the beginning of an entity’s reign.
-
E.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede8eac081908dffade6a5e7950b |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.