Triple
T21321558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eileen Prince |
E525629
|
entity |
| Predicate | relationshipToTobiasSnape |
P143712
|
FINISHED |
| Object | wife |
—
|
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: wife | Statement: [Eileen Prince, relationshipToTobiasSnape, wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToTobiasSnape Context triple: [Eileen Prince, relationshipToTobiasSnape, wife]
-
A.
relationshipToSeverusSnape
Indicates the specific personal or social connection an entity has with Severus Snape.
-
B.
relationshipToEileenSnape
Indicates the specific familial, social, or personal relationship that one entity has to Eileen Snape.
-
C.
relationshipToAgnesAndTobias
Indicates the specific familial, social, or other relational connection that an entity has to the pair Agnes and Tobias considered together.
-
D.
relationshipToAberforthDumbledore
Indicates the specific familial or social relationship an entity has to Aberforth Dumbledore.
-
E.
relationshipToMinervaMcGonagall
Indicates the specific familial, social, or professional relationship that an entity has to Minerva McGonagall.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed1538c8190954da114e49dfa36 |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:39 p.m.