Triple
T38147567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eadberht I of Kent |
E952659
|
entity |
| Predicate | siblingOrCloseKinsman |
P132967
|
FINISHED |
| Object | Æðelberht II of Kent |
—
|
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: Æðelberht II of Kent | Statement: [Eadberht I of Kent, siblingOrCloseKinsman, Æðelberht II of Kent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingOrCloseKinsman Context triple: [Eadberht I of Kent, siblingOrCloseKinsman, Æðelberht II of Kent]
-
A.
siblingOrRelative
chosen
Indicates that two entities are related to each other by blood, marriage, or family ties, including but not limited to being siblings.
-
B.
brotherInLaw
Indicates a relationship where one person is the brother of someone's spouse, the spouse of someone's sibling, or the spouse of the sibling of someone's spouse.
-
C.
nieceOrNephewOf
Indicates that one person is the niece or nephew (the child of a sibling or sibling-in-law) of another person.
-
D.
spouseOfSiblingOf
Indicates the person who is married to someone’s sibling.
-
E.
isNephewOf
Indicates that one person is the male child of another person's sibling.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.