Triple
T16169266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lauderdale |
E392389
|
entity |
| Predicate | subsidiaryTitle |
P1916
|
FINISHED |
| Object |
Lord Thirlestane
Lord Thirlestane is a Scottish noble title historically associated with the Lauderdale peerage and the Maitland family.
|
E430191
|
NE FINISHED |
How this triple was built (4 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: Lord Thirlestane | Statement: [Earl of Lauderdale, subsidiaryTitle, Lord Thirlestane]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lord Thirlestane Context triple: [Earl of Lauderdale, subsidiaryTitle, Lord Thirlestane]
-
A.
Lord Crichton
Lord Crichton is a hereditary Scottish noble title historically associated with the influential Crichton family.
-
B.
Lord Maitland of Thirlestane
Lord Maitland of Thirlestane is a Scottish peerage title historically associated with the influential Lauderdale branch of the Maitland family.
-
C.
Lord Haddo
Lord Haddo is a courtesy title traditionally borne by the heir apparent to the Earl of Aberdeen in the Scottish peerage.
-
D.
Lord Reay
Lord Reay is a Scottish peerage title historically held by the chiefs of Clan Mackay, a prominent Highland clan from the far north of Scotland.
-
E.
Lord Fife
Lord Fife is the courtesy title historically associated with the Scottish noble family of Duff, particularly the Earls of Fife.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lord Thirlestane Triple: [Earl of Lauderdale, subsidiaryTitle, Lord Thirlestane]
Generated description
Lord Thirlestane is a Scottish noble title historically associated with the Lauderdale peerage and the Maitland family.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lord Thirlestane Target entity description: Lord Thirlestane is a Scottish noble title historically associated with the Lauderdale peerage and the Maitland family.
-
A.
Lord Crichton
Lord Crichton is a hereditary Scottish noble title historically associated with the influential Crichton family.
-
B.
Lord Maitland of Thirlestane
chosen
Lord Maitland of Thirlestane is a Scottish peerage title historically associated with the influential Lauderdale branch of the Maitland family.
-
C.
Lord Haddo
Lord Haddo is a courtesy title traditionally borne by the heir apparent to the Earl of Aberdeen in the Scottish peerage.
-
D.
Lord Reay
Lord Reay is a Scottish peerage title historically held by the chiefs of Clan Mackay, a prominent Highland clan from the far north of Scotland.
-
E.
Lord Fife
Lord Fife is the courtesy title historically associated with the Scottish noble family of Duff, particularly the Earls of Fife.
- F. None of above.
Provenance (5 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb5e6d881908749683091afa90c |
completed | April 17, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7bb6aac8190a33607abfe9a32d0 |
completed | May 10, 2026, 3:12 a.m. |
| NEDg | Description generation | batch_69fff9bb09c48190881c0f70bae0aec8 |
completed | May 10, 2026, 3:21 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fffa5186b88190971d3c5061503541 |
completed | May 10, 2026, 3:24 a.m. |
Created at: April 10, 2026, 5:02 a.m.