Triple
T6217232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Lancaster, 1st Duke of Bedford |
E139018
|
entity |
| Predicate | periodOfRegency |
P68958
|
FINISHED |
| Object | 1422–1435 |
—
|
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: 1422–1435 | Statement: [John of Lancaster, 1st Duke of Bedford, periodOfRegency, 1422–1435]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfRegency Context triple: [John of Lancaster, 1st Duke of Bedford, periodOfRegency, 1422–1435]
-
A.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
B.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
regencyBeganAfter
Indicates that the start of one regency occurred later in time than the start of another regency.
-
E.
regent
Indicates that one entity serves as the regent, exercising ruling authority on behalf of another (typically a monarch or state), usually during a period when the rightful ruler is unable to govern.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a35e308190be25c41b02704411 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:21 p.m.