Triple

T1393018
Position Surface form Disambiguated ID Type / Status
Subject Milliways E30602 entity
Predicate locatedInFictionalPlace P21117 FINISHED
Object the future of the universe 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: the future of the universe | Statement: [Milliways, locatedInFictionalPlace, the future of the universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInFictionalPlace
Context triple: [Milliways, locatedInFictionalPlace, the future of the universe]
  • A. locatedInFictionalCountry
    Indicates that an entity exists or is situated within a country that is fictional rather than real.
  • B. hasFictionalLocation chosen
    Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
  • C. fictionalUniverseLocation
    Indicates that one entity is a location or setting within the fictional universe to which the other entity belongs or in which it takes place.
  • D. setInFictionalLocation
    Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
  • E. partOfFictionalCity
    Indicates that one entity is a component, area, or subdivision within a larger fictional city.
  • 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_69a498fd4e408190bd73eca30ea9754c completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c360a7f08190ab7e903764b06fdf completed March 1, 2026, 10:53 p.m.
PD Predicate disambiguation batch_69a4beffcf808190ab4cd0271257ce63 completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:59 p.m.