Triple
T5705251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Monck, 1st Duke of Albemarle |
E125767
|
entity |
| Predicate | yearCreatedDuke |
P65689
|
FINISHED |
| Object | 1660 |
—
|
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: 1660 | Statement: [George Monck, 1st Duke of Albemarle, yearCreatedDuke, 1660]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearCreatedDuke Context triple: [George Monck, 1st Duke of Albemarle, yearCreatedDuke, 1660]
-
A.
createdDukeOfYorkBy
Indicates the action by which an authority or agent formally conferred or established the title of Duke of York upon a person.
-
B.
establishedAsDukes
Indicates that certain individuals or entities were formally created or recognized with the rank and title of dukes.
-
C.
createdDukeOfFifeBy
Indicates that one entity conferred or established the title "Duke of Fife" upon another entity.
-
D.
createdDukeOfElchingen
Indicates the act of conferring the noble title "Duke of Elchingen" upon a person, thereby creating or establishing that dukedom for them.
-
E.
boroughCreationYear
Indicates the year in which a borough was officially established or created.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02459cd18819080fda0b481d11f08 |
completed | March 22, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c023dfec6881909ee6189b874b4348 |
completed | March 22, 2026, 5:16 p.m. |
Created at: March 22, 2026, 3:45 p.m.