Triple
T31626194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Time Tunnel |
E807030
|
entity |
| Predicate | notableEpisodeSetting |
P134922
|
FINISHED |
| Object | Titanic |
E1554800
|
NE 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: Titanic | Statement: [The Time Tunnel, notableEpisodeSetting, Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEpisodeSetting Context triple: [The Time Tunnel, notableEpisodeSetting, Titanic]
-
A.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
B.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
C.
notableEpisodeEvent
Indicates that an event is especially significant or noteworthy within the context of a particular episode.
-
D.
notableAsSettingOf
chosen
Indicates that a place or environment is recognized as the setting where the events of a particular work (e.g., book, film, story) take place.
-
E.
notableShowLocation
Indicates that a show or performance is notably associated with, took place at, or is best known for occurring in a particular location.
- F. None of above.
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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b565a66388190af7c640ac260ef0d |
completed | June 12, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:43 p.m.