Triple
T20702890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steward of Scotland |
E508825
|
entity |
| Predicate | officeStatusByLateMiddleAges |
P141155
|
FINISHED |
| Object | subsumed into royal dignity |
—
|
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: subsumed into royal dignity | Statement: [Steward of Scotland, officeStatusByLateMiddleAges, subsumed into royal dignity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStatusByLateMiddleAges Context triple: [Steward of Scotland, officeStatusByLateMiddleAges, subsumed into royal dignity]
-
A.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
-
B.
endAgeMa
Indicates the age (in years) at which a marriage or marital relationship ends.
-
C.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
-
D.
medianAgeHigherThan
Indicates that the median age of one group, population, or set is greater than the median age of another.
-
E.
ageBased
Indicates a relationship or condition that depends on or is determined by the age of the entities involved.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c18cb9cc819095d0669dca037424 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:13 p.m.