Triple
T21257191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobias Snape |
E523898
|
entity |
| Predicate | relationshipToSeverusSnape |
P143406
|
FINISHED |
| Object | Father |
—
|
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: Father | Statement: [Tobias Snape, relationshipToSeverusSnape, Father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSeverusSnape Context triple: [Tobias Snape, relationshipToSeverusSnape, Father]
-
A.
relationshipToMinervaMcGonagall
Indicates the specific familial, social, or professional relationship that an entity has to Minerva McGonagall.
-
B.
relationshipToAberforthDumbledore
Indicates the specific familial or social relationship an entity has to Aberforth Dumbledore.
-
C.
relationshipToHarry
Indicates the specific type of relationship or connection that an entity has to Harry.
-
D.
relationshipTypeWithRubeusHagrid
Indicates the specific nature or category of the relationship an entity has with Rubeus Hagrid (e.g., friend, colleague, student, family).
-
E.
relationshipToHeadmaster
Indicates the specific type of personal or professional relationship an entity has with the headmaster.
- F. None of above. chosen
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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e2f1d48190b566ab4d736fdbc4 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:58 p.m.