Triple

T33232108
Position Surface form Disambiguated ID Type / Status
Subject The Runaway Skyscraper E850721 entity
Predicate fictionalTimePeriodVisited P186300 FINISHED
Object prehistoric Earth 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: prehistoric Earth | Statement: [The Runaway Skyscraper, fictionalTimePeriodVisited, prehistoric Earth]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalTimePeriodVisited
Context triple: [The Runaway Skyscraper, fictionalTimePeriodVisited, prehistoric Earth]
  • A. fictionalTime
    Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
  • B. existsInFictionalTimePeriod chosen
    Indicates that an entity is situated within, or associated with, a time period that is fictional rather than part of real-world history.
  • C. fictionalTimeDepth
    Indicates a relationship where an entity is associated with a time period or temporal depth that exists only within a fictional or imagined context.
  • D. hasFictionalTimeAfter
    Indicates that one fictional time point or period occurs later than another within a narrative or imagined timeline.
  • E. periodOfFictionalSetting
    Indicates the time period in which the events of a fictional work are set.
  • 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_69f349613f988190a1eb75467d167122 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fe5c1a502081909d4024e514309c8e completed May 8, 2026, 9:56 p.m.
PD Predicate disambiguation batch_69fe5a9df21c819087153f5d0bcaa987 completed May 8, 2026, 9:50 p.m.
Created at: May 1, 2026, 1:30 a.m.