Triple
T2214473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Bull of 1356 |
E50992
|
entity |
| Predicate | validUntil |
P33304
|
FINISHED |
| Object | end of the Holy Roman Empire in 1806 |
—
|
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: end of the Holy Roman Empire in 1806 | Statement: [Golden Bull of 1356, validUntil, end of the Holy Roman Empire in 1806]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validUntil Context triple: [Golden Bull of 1356, validUntil, end of the Holy Roman Empire in 1806]
-
A.
usedUntil
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
C.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
D.
validityPeriodForAdults
Indicates the time span during which something is considered valid or applicable specifically for adults.
-
E.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfef875c8190b642736b4cc11d4c |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.