Triple
T142593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George III of the United Kingdom |
E2884
|
entity |
| Predicate | regencyPeriod |
P4210
|
FINISHED |
| Object | 1811-02-05/1820-01-29 |
—
|
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: 1811-02-05/1820-01-29 | Statement: [George III of the United Kingdom, regencyPeriod, 1811-02-05/1820-01-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regencyPeriod Context triple: [George III of the United Kingdom, regencyPeriod, 1811-02-05/1820-01-29]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
periodOfRule
chosen
Indicates the span of time during which an entity exercised authority, control, or governance over something.
-
C.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
D.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
E.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565559ac81909e0c4e095a7dfa27 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.