Triple
T35849964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rape of Tamar |
E1036320
|
entity |
| Predicate | hasFatherOfMainCharacters |
P123134
|
FINISHED |
| Object | King David |
E3231
|
NE 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: King David | Statement: [Rape of Tamar, hasFatherOfMainCharacters, King David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFatherOfMainCharacters Context triple: [Rape of Tamar, hasFatherOfMainCharacters, King David]
-
A.
hasFatherFigure
Indicates that one entity serves as a paternal or father-like figure to another entity, regardless of biological relation.
-
B.
hasFictionalFamilyMember
Indicates that one entity has another entity as a family member within a fictional or imagined context.
-
C.
hasProtagonistFamilyMember
chosen
Indicates that a work’s protagonist has a specified individual as a member of their family.
-
D.
hasFictionalFather
Indicates that one entity is the fictional father of another entity.
-
E.
appearsAsChildOfMainCharacters
Indicates that an entity is depicted or presented as the child of the story’s main characters.
- F. None of above.
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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4e49c6081908130e76dfa3b1a59 |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:06 p.m.