Triple
T30773659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Dalkeith |
E783597
|
entity |
| Predicate | linkedDucalTitle |
P75216
|
FINISHED |
| Object | Duke of Queensberry |
—
|
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: Duke of Queensberry | Statement: [Earl of Dalkeith, linkedDucalTitle, Duke of Queensberry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedDucalTitle Context triple: [Earl of Dalkeith, linkedDucalTitle, Duke of Queensberry]
-
A.
linkedDukedom
chosen
Indicates a relationship where one dukedom is formally connected or associated with another dukedom.
-
B.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
C.
aristocraticTitleByMarriage
Indicates that an individual holds an aristocratic title acquired through marriage rather than by birth or independent grant.
-
D.
lostDucalTitle
Indicates that an entity that once held a ducal title has had that title taken away, relinquished, or otherwise ceased to possess it.
-
E.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 8:40 p.m.