Triple
T36785635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jason Nesmith |
E908902
|
entity |
| Predicate | fictionalShow |
P57669
|
FINISHED |
| Object | Galaxy Quest (in-universe TV 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: Galaxy Quest (in-universe TV series) | Statement: [Jason Nesmith, fictionalShow, Galaxy Quest (in-universe TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalShow Context triple: [Jason Nesmith, fictionalShow, Galaxy Quest (in-universe TV series)]
-
A.
hasFictionalShowWithinShow
chosen
Indicates that one show contains or features another fictional show within its narrative.
-
B.
fictionalType
Indicates that one entity is a fictional or imaginary type or category of the other entity.
-
C.
fictionalBroadcastType
Indicates that the relationship specifies the type or category of a fictional broadcast associated with an entity.
-
D.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
E.
fictionalMedium
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:12 p.m.