Triple
T19985524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Care of Magical Creatures |
E493920
|
entity |
| Predicate | notableCreatureStudied |
P138207
|
FINISHED |
| Object | Hippogriff |
—
|
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: Hippogriff | Statement: [Care of Magical Creatures, notableCreatureStudied, Hippogriff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCreatureStudied Context triple: [Care of Magical Creatures, notableCreatureStudied, Hippogriff]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableModelOrganism
Indicates that an organism is widely recognized and frequently used as a standard or reference model for scientific research or experimentation.
-
C.
studiedOrganism
Indicates that an entity conducted study or research on a particular organism.
-
D.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
E.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d162b008190a18d325796d75d77 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:29 p.m.