Triple
T33659041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuzzy Sapiens |
E862300
|
entity |
| Predicate | hasFictionalSpeciesRole |
P180853
|
FINISHED |
| Object | Fuzzies as central protagonists |
—
|
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: Fuzzies as central protagonists | Statement: [Fuzzy Sapiens, hasFictionalSpeciesRole, Fuzzies as central protagonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalSpeciesRole Context triple: [Fuzzy Sapiens, hasFictionalSpeciesRole, Fuzzies as central protagonists]
-
A.
fictionalSpecies
Indicates that the subject is a species that exists only in fiction or imaginary works, rather than in real life.
-
B.
fictionalPerformerSpecies
Indicates that a performer in a fictional work belongs to, or is characterized as, a particular fictional species.
-
C.
associatedCharacterSpecies
Indicates that one entity is related to, or linked with, the species of a particular character.
-
D.
hasSpeciesInFiction
chosen
Indicates that a fictional work or universe features a particular species as part of its narrative or setting.
-
E.
characterSpeciesPortrayed
Indicates that a character is portrayed as belonging to a particular species.
- F. None of above.
Provenance (3 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:42 a.m.