Triple
T13414279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Berry |
E313168
|
entity |
| Predicate | createdAsDuchy |
P109814
|
FINISHED |
| Object | 1360 |
—
|
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: 1360 | Statement: [Duchy of Berry, createdAsDuchy, 1360]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsDuchy Context triple: [Duchy of Berry, createdAsDuchy, 1360]
-
A.
duchyFoundedBy
Indicates that a particular duchy was established or created by a specific person, group, or authority.
-
B.
createdDukeOfRichmondBy
Indicates the act by which an authority formally established or conferred the title of Duke of Richmond upon a person.
-
C.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
-
D.
createdDukeOfRichmondDate
Indicates the date on which the title of Duke of Richmond was created or conferred.
-
E.
createdDukeOfYork
Indicates the action of appointing or establishing someone in the noble title or rank of Duke of York.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb556948190af008c88e5bbf051 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:39 p.m.