Triple
T34957290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varith |
E1008151
|
entity |
| Predicate | notAppearsIn |
P150264
|
FINISHED |
| Object | Star Trek: Voyager television series |
—
|
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: Star Trek: Voyager television series | Statement: [Varith, notAppearsIn, Star Trek: Voyager television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAppearsIn Context triple: [Varith, notAppearsIn, Star Trek: Voyager television series]
-
A.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
-
B.
notObservedOn
Indicates that a particular entity, event, or condition was explicitly not observed or recorded at a specified time or context.
-
C.
notListedOn
chosen
Indicates that an entity is absent from, or does not appear in, a specified list, registry, or catalog.
-
D.
notWithin
Indicates that one entity is located outside the spatial or conceptual bounds of another entity.
-
E.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.