Triple
T32226784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph II, Holy Roman Emperor |
E823222
|
entity |
| Predicate | coRegencyPeriod |
P68958
|
FINISHED |
| Object | 1765-1780 |
—
|
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: 1765-1780 | Statement: [Joseph II, Holy Roman Emperor, coRegencyPeriod, 1765-1780]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRegencyPeriod Context triple: [Joseph II, Holy Roman Emperor, coRegencyPeriod, 1765-1780]
-
A.
includesRegency
Indicates that one entity’s scope, period, or authority encompasses or contains a regency associated with another entity.
-
B.
regency
Indicates that one entity exercises ruling authority on behalf of another, typically when the latter is unable to govern directly (such as due to minority, absence, or incapacity).
-
C.
partOfRegency
Indicates that one entity functions as a regent or governing authority on behalf of, or as a component of, a larger regency arrangement associated with another entity.
-
D.
periodOfRegency
chosen
Indicates the time span during which a regent exercised authority on behalf of the rightful ruler.
-
E.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbcbd31c8190a482a5fd5040410d |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.