Triple
T24139950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æthelstan of Kent |
E598199
|
entity |
| Predicate | likelyBirthOrder |
P20593
|
FINISHED |
| Object | eldest son of Æthelwulf of Wessex |
—
|
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: eldest son of Æthelwulf of Wessex | Statement: [Æthelstan of Kent, likelyBirthOrder, eldest son of Æthelwulf of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyBirthOrder Context triple: [Æthelstan of Kent, likelyBirthOrder, eldest son of Æthelwulf of Wessex]
-
A.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
B.
orderOfBirth
Indicates the relative sequence in which entities are born, specifying who is earlier or later in birth order.
-
C.
willBeBornAs
Indicates that an entity is predicted or destined to come into existence in the future as a particular individual or form.
-
D.
positionInLineOfSuccessionAtBirth
Indicates the ordinal place an individual held in a defined line of succession at the moment of their birth.
-
E.
birthPromisedBy
Indicates that one entity has pledged or foretold the future birth of another entity.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e005f7f48190b2c538bfc79a83b2 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:28 p.m.