Triple
T32430056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Upper Lotharingia |
E828694
|
entity |
| Predicate | firstRulerStartDate |
P206279
|
FINISHED |
| Object | 959 |
—
|
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: 959 | Statement: [Duchy of Upper Lotharingia, firstRulerStartDate, 959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRulerStartDate Context triple: [Duchy of Upper Lotharingia, firstRulerStartDate, 959]
-
A.
firstMonarchOfCurrentDynastyReignStart
Indicates the date or time when the reign of the first monarch of the current ruling dynasty began.
-
B.
monarchicalPeriodStart
Indicates the point in time when a monarchy or monarchical rule over an entity begins.
-
C.
firstEmperorReignStart
Indicates the date or time when the reign of the first emperor over a given realm or polity began.
-
D.
firstMonarch
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
E.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
- F. None of above. chosen
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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:54 a.m.