Triple
T26498346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sean Jones |
E669345
|
entity |
| Predicate | relationshipToNevilleFlynn |
P196975
|
FINISHED |
| Object | person under protection |
—
|
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: person under protection | Statement: [Sean Jones, relationshipToNevilleFlynn, person under protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNevilleFlynn Context triple: [Sean Jones, relationshipToNevilleFlynn, person under protection]
-
A.
relationshipToAberforthDumbledore
Indicates the specific familial or social relationship an entity has to Aberforth Dumbledore.
-
B.
relationshipToHarry
Indicates the specific type of relationship or connection that an entity has to Harry.
-
C.
relationshipToSeverusSnape
Indicates the specific personal or social connection an entity has with Severus Snape.
-
D.
relationshipToMinervaMcGonagall
Indicates the specific familial, social, or professional relationship that an entity has to Minerva McGonagall.
-
E.
relationshipTypeWithRubeusHagrid
Indicates the specific nature or category of the relationship an entity has with Rubeus Hagrid (e.g., friend, colleague, student, family).
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
| PDg | Predicate description generation | batch_69fe72db8810819089e397961b8ead7a |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 27, 2026, 1:10 a.m.