Triple
T27315817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athelstan Atheling |
E689342
|
entity |
| Predicate | royalLine |
P57937
|
FINISHED |
| Object | descendant of King Edgar the Peaceful |
—
|
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: descendant of King Edgar the Peaceful | Statement: [Athelstan Atheling, royalLine, descendant of King Edgar the Peaceful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalLine Context triple: [Athelstan Atheling, royalLine, descendant of King Edgar the Peaceful]
-
A.
relatedRoyalHouse
Indicates a relationship where one royal house is historically, genealogically, or politically connected to another royal house.
-
B.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
C.
royalTribe
Indicates that an entity belongs to, descends from, or is associated with a tribe that holds royal or ruling status.
-
D.
hasRoyalAncestryFrom
chosen
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
E.
heirThroughFemaleLine
Indicates that one entity is the heir of another specifically through a lineage traced via female ancestors.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:30 a.m.