Triple
T20214272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akane |
E493574
|
entity |
| Predicate | inUniverseSpecies |
P37702
|
FINISHED |
| Object | host |
—
|
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: host | Statement: [Akane, inUniverseSpecies, host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseSpecies Context triple: [Akane, inUniverseSpecies, host]
-
A.
inUniverseOwnerSpecies
Indicates that a particular species is recognized as the canonical or in-universe owner of something within a fictional or defined universe.
-
B.
speciesInUniverse
chosen
Indicates that a given species exists within, or is a member of, a particular fictional or defined universe.
-
C.
speciesNameInUniverse
Indicates that a given name is the designated species name within a particular fictional or defined universe.
-
D.
alienSpeciesName
Indicates that an entity is identified by the proper name of an alien species.
-
E.
fictionalSpecies
Indicates that the subject is a species that exists only in fiction or imaginary works, rather than in real life.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed8101081908e53a8bde48624b1 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.