Triple
T216081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Restaurant at the End of the Universe |
E4107
|
entity |
| Predicate | settingFeature |
P1957
|
FINISHED |
| Object | end of time |
—
|
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: end of time | Statement: [The Restaurant at the End of the Universe, settingFeature, end of time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingFeature Context triple: [The Restaurant at the End of the Universe, settingFeature, end of time]
-
A.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
C.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.