Triple
T30840782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton-Gordon |
E785501
|
entity |
| Predicate | linkedToPeerageTitle |
P64418
|
FINISHED |
| Object | Peerage of Scotland |
—
|
NE NERFINISHED |
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: Peerage of Scotland | Statement: [Hamilton-Gordon, linkedToPeerageTitle, Peerage of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToPeerageTitle Context triple: [Hamilton-Gordon, linkedToPeerageTitle, Peerage of Scotland]
-
A.
linkedToPeerage
chosen
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
B.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
hasPeerageTitle
Indicates that an entity holds or is associated with a formal noble or aristocratic title within a peerage system.
-
D.
titleHolderOfficeBeforePeerage
Indicates that the person holding a title previously held a specific office before being elevated to the peerage.
-
E.
laterPeerageConnections
Indicates that one entity acquires or forms peerage-related ties (such as titles, ranks, or noble associations) at a later time or stage in relation to another entity.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 8:45 p.m.