Triple
T16565670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Hamilton, 8th Duke of Hamilton |
E402452
|
entity |
| Predicate | hasNoSurvivingLegitimateIssue |
P124078
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Douglas Hamilton, 8th Duke of Hamilton, hasNoSurvivingLegitimateIssue, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSurvivingLegitimateIssue Context triple: [Douglas Hamilton, 8th Duke of Hamilton, hasNoSurvivingLegitimateIssue, true]
-
A.
hasNoIssue
Indicates that there are no problems, defects, or conflicts associated with the referenced entity or situation.
-
B.
noLegitimateIssue
Indicates that there is no valid, substantive, or legally recognized issue or dispute present in the given context.
-
C.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
D.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
E.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e357711ea481909468147375051bb4 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.