Triple
T31675363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis II |
E808384
|
entity |
| Predicate | startTimeAsEmperor |
P35128
|
FINISHED |
| Object | 855 |
—
|
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: 855 | Statement: [Louis II, startTimeAsEmperor, 855]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsEmperor Context triple: [Louis II, startTimeAsEmperor, 855]
-
A.
startEmperor
chosen
Indicates that an entity begins its role, reign, or status as an emperor.
-
B.
endTimeAsEmperor
Indicates the point in time at which an individual’s reign or tenure as emperor comes to an end.
-
C.
declaredHimselfEmperorInYear
Indicates that a person formally proclaimed himself to be emperor in a specific year.
-
D.
reigningEmperorAtStart
Indicates that the subject was the emperor in power at the beginning of a specified period or event.
-
E.
reignAsTitularEmperorStart
Indicates the point in time when an individual begins to hold the title and status of emperor in name, without necessarily exercising actual governing power.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 30, 2026, 11:02 p.m.