Triple
T1799905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantastic Voyage |
E39691
|
entity |
| Predicate | timeSpanOfFictionalEvents |
P10692
|
FINISHED |
| Object | 60 minutes inside the human body |
—
|
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: 60 minutes inside the human body | Statement: [Fantastic Voyage, timeSpanOfFictionalEvents, 60 minutes inside the human body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanOfFictionalEvents Context triple: [Fantastic Voyage, timeSpanOfFictionalEvents, 60 minutes inside the human body]
-
A.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
B.
storyTimeSpanInFilm
chosen
Indicates the duration of time that the story or narrative covers within the film.
-
C.
fictionalAge
Indicates the age attributed to an entity within a fictional or narrative context, rather than its real-world age.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
timeOfNarrative
Indicates the specific time or period during which the events of a narrative are set or unfold.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.