Triple
T13016011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kendra Dumbledore |
E322552
|
entity |
| Predicate | relationshipToAlbusDumbledore |
P82369
|
FINISHED |
| Object | mother |
—
|
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: mother | Statement: [Kendra Dumbledore, relationshipToAlbusDumbledore, mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAlbusDumbledore Context triple: [Kendra Dumbledore, relationshipToAlbusDumbledore, mother]
-
A.
relationshipTypeWithRubeusHagrid
Indicates the specific nature or category of the relationship an entity has with Rubeus Hagrid (e.g., friend, colleague, student, family).
-
B.
relationshipToHeadmaster
chosen
Indicates the specific type of personal or professional relationship an entity has with the headmaster.
-
C.
roleInHarryPotter
Indicates that one entity has a specific role or character part within the Harry Potter series in relation to the other entity.
-
D.
relationshipToHarryMonroe
Indicates the specific type of personal, social, or familial relationship that one entity has to Harry Monroe.
-
E.
relationshipToHarryBright
Indicates that one entity has a specified personal or familial relationship to the person identified as Harry Bright.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecd04748190ade2530ee5db35fe |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:50 p.m.