Triple
T3828438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton family (Dukes of Hamilton) |
E88748
|
entity |
| Predicate | establishedAsDukes |
P52219
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Hamilton family (Dukes of Hamilton), establishedAsDukes, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsDukes Context triple: [Hamilton family (Dukes of Hamilton), establishedAsDukes, 17th century]
-
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.
duchyEstablished
Indicates that a duchy was formally created or founded at a particular time or under specific circumstances.
-
C.
reignAsDukeOfNassauStart
Indicates the time at which an individual begins their tenure ruling in the position of Duke of Nassau.
-
D.
reignAsDukeOfYorkEnd
Indicates the point in time or event at which an individual’s tenure or rule as Duke of York comes to an end.
-
E.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:17 p.m.