Triple
T15174579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Douglas, 14th Earl of Morton |
E362571
|
entity |
| Predicate | titleIs |
P15922
|
FINISHED |
| Object | 14th holder of the Morton earldom |
—
|
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: 14th holder of the Morton earldom | Statement: [James Douglas, 14th Earl of Morton, titleIs, 14th holder of the Morton earldom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleIs Context triple: [James Douglas, 14th Earl of Morton, titleIs, 14th holder of the Morton earldom]
-
A.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
C.
titles
chosen
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
D.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
E.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0066236d481909e8ac47f496861ad |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.