Triple
T32843520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ship in a Bottle |
E840034
|
entity |
| Predicate | featuresHolodeckProgram |
P57670
|
FINISHED |
| Object | Sherlock Holmes simulation |
—
|
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: Sherlock Holmes simulation | Statement: [Ship in a Bottle, featuresHolodeckProgram, Sherlock Holmes simulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHolodeckProgram Context triple: [Ship in a Bottle, featuresHolodeckProgram, Sherlock Holmes simulation]
-
A.
featuresFictionalProgram
chosen
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
B.
programFeature
Indicates that a particular feature, capability, or component is part of, supported by, or provided within a given program.
-
C.
framedAsHolodeckProgramFromEpisode
Indicates that something is presented or depicted as a holodeck program originating from a specific episode.
-
D.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
E.
hasHolodeck
Indicates that an entity possesses or includes a holodeck facility or feature.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: May 1, 2026, 1:16 a.m.