Triple
T31625868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad II |
E807021
|
entity |
| Predicate | reignStartAsKingOfGermany |
P36565
|
FINISHED |
| Object | 1024 |
—
|
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: 1024 | Statement: [Conrad II, reignStartAsKingOfGermany, 1024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignStartAsKingOfGermany Context triple: [Conrad II, reignStartAsKingOfGermany, 1024]
-
A.
reignAsKingOfGermanyStart
chosen
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
B.
reignStartAsGermanEmperor
Indicates the time at which an individual began their rule in the role of German Emperor.
-
C.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
-
D.
reignStartAsKingOfBavaria
Indicates the date or point in time when an individual began their reign as King of Bavaria.
-
E.
reignStartAsKingOfEastFrancia
Indicates the date or event when an individual began their reign as king of East Francia.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 30, 2026, 10:43 p.m.