Triple
T32114609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radagast |
E820202
|
entity |
| Predicate | speciesInAdaptations |
P181268
|
FINISHED |
| Object | Human-like wizard |
—
|
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: Human-like wizard | Statement: [Radagast, speciesInAdaptations, Human-like wizard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesInAdaptations Context triple: [Radagast, speciesInAdaptations, Human-like wizard]
-
A.
hasAquaticAdaptationsIn
Indicates that an entity possesses physical or behavioral adaptations suited for living or functioning in a specified aquatic environment.
-
B.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
C.
hasHumanAdaptation
Indicates that something has been modified, designed, or adjusted specifically to suit human use, abilities, or needs.
-
D.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
-
E.
speciesType
Indicates the specific biological species category to which an entity belongs.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: May 1, 2026, 12:28 a.m.