Triple
T13534316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan Sutherland |
E323219
|
entity |
| Predicate | ducalTitleCreation |
P31263
|
FINISHED |
| Object | Dukedom of Sutherland created in 1833 |
—
|
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: Dukedom of Sutherland created in 1833 | Statement: [Clan Sutherland, ducalTitleCreation, Dukedom of Sutherland created in 1833]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ducalTitleCreation Context triple: [Clan Sutherland, ducalTitleCreation, Dukedom of Sutherland created in 1833]
-
A.
nobleTitleCreationDate
chosen
Indicates the date on which a particular noble title was formally created or granted.
-
B.
createdAsDuchy
Indicates that an entity was established or formed with the political status or rank of a duchy.
-
C.
aristocraticTitleCreationReason
Indicates the reason or circumstance under which an aristocratic title was created or granted.
-
D.
ducalReignStart
Indicates the point in time when an individual begins their tenure or rule as a duke.
-
E.
aristocraticTitlePassedTo
Indicates that an aristocratic title is transferred or inherited from one person to another.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbcad2881909fb7490311807f75 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.