Triple
T20211133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagini |
E493487
|
entity |
| Predicate | bloodTypeRole |
P139226
|
FINISHED |
| Object | source of venom for Nagini's bite injuries |
—
|
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: source of venom for Nagini's bite injuries | Statement: [Nagini, bloodTypeRole, source of venom for Nagini's bite injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodTypeRole Context triple: [Nagini, bloodTypeRole, source of venom for Nagini's bite injuries]
-
A.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
B.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
C.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
D.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
E.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:38 p.m.