Triple
T29016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Southesk |
E578
|
entity |
| Predicate | hereditaryPeerage |
P1913
|
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: [Earl of Southesk, hereditaryPeerage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryPeerage Context triple: [Earl of Southesk, hereditaryPeerage, true]
-
A.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
B.
isOrderOfKnighthood
Indicates that an entity is a formal chivalric or knightly order to which individuals can be admitted.
-
C.
hasHeraldicFamily
Indicates that an entity is associated with a particular heraldic family or lineage, typically sharing the same coat of arms or heraldic identity.
-
D.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
E.
isOldestRankOfKnighthoodIn
Indicates that a particular rank of knighthood is the most senior or highest-ranking within a specified order, system, or jurisdiction.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486d40348190b2d21fc444f499a6 |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a248fef2b881908180bd4e32e58cb5 |
completed | Feb. 28, 2026, 1:46 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.