Triple
T32132313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vixen (web series) |
E820683
|
entity |
| Predicate | characterUses |
P197987
|
FINISHED |
| Object | Tantu Totem |
—
|
NE NERFINISHED |
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: Tantu Totem | Statement: [Vixen (web series), characterUses, Tantu Totem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterUses Context triple: [Vixen (web series), characterUses, Tantu Totem]
-
A.
characters
Indicates that one entity is a character (or set of characters) associated with, appearing in, or belonging to another entity (such as a work, story, or medium).
-
B.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
D.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
E.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: May 1, 2026, 12:29 a.m.