Triple
T23280511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Æthelhelm |
E588846
|
entity |
| Predicate | possibleSon |
P42547
|
FINISHED |
| Object | Æthelfrith of Mercia |
—
|
NE NERFINISHED |
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: Æthelfrith of Mercia | Statement: [Æthelhelm, possibleSon, Æthelfrith of Mercia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleSon Context triple: [Æthelhelm, possibleSon, Æthelfrith of Mercia]
-
A.
possibleDaughter
Indicates that one entity may be the daughter of another, but this relationship is not certain or confirmed.
-
B.
possibleDescendant
Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
-
C.
possibleFamily
Indicates that two entities could plausibly be related as members of the same family, though the familial relationship is not confirmed.
-
D.
possibleRelative
chosen
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
E.
possibleMother
Indicates that one entity could be the biological or adoptive mother of another, but this relationship is uncertain or not definitively established.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:55 p.m.