Triple
T35409387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Ker, 1st Duke of Roxburghe |
E1023463
|
entity |
| Predicate | createdDukeIn |
P75440
|
FINISHED |
| Object | 1707 |
—
|
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: 1707 | Statement: [John Ker, 1st Duke of Roxburghe, createdDukeIn, 1707]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdDukeIn Context triple: [John Ker, 1st Duke of Roxburghe, createdDukeIn, 1707]
-
A.
createdDukeOn
chosen
Indicates that an entity established or founded the title or position of Duke on a specific date or occasion.
-
B.
createdDukeBy
Indicates that an entity was made a duke (granted the ducal title or rank) by another specific entity.
-
C.
createdDukeOfYork
Indicates the action of appointing or establishing someone in the noble title or rank of Duke of York.
-
D.
createdDukeOfLeinster
Indicates that one entity formally granted or established the title "Duke of Leinster" for another entity.
-
E.
createdDukeOfElchingen
Indicates the act of conferring the noble title "Duke of Elchingen" upon a person, thereby creating or establishing that dukedom for them.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 3, 2026, 4:03 p.m.