Triple

T36167106
Position Surface form Disambiguated ID Type / Status
Subject Alex Steiner E1046035 entity
Predicate locatedInFictionalTime P186300 FINISHED
Object World War II E32 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: World War II | Statement: [Alex Steiner, locatedInFictionalTime, World War II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInFictionalTime
Context triple: [Alex Steiner, locatedInFictionalTime, World War II]
  • A. 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.
  • B. locatedInFictionalEvent
    Indicates that one entity (typically a place, object, or character) exists or occurs within the context or setting of a fictional event.
  • C. locatedInFictionalContext
    Indicates that one entity exists or occurs within the setting or universe of a fictional work associated with another entity.
  • D. fictionalTime
    Indicates that the associated time or temporal reference exists only within a fictional or imagined context, rather than in real-world chronology.
  • E. residesInFictionalLocation
    Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
  • 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_69f76e396bc88190b99d221bff9be27a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a390d3e5e948190b20be728f76236ac completed June 22, 2026, 10:23 a.m.
PD Predicate disambiguation batch_6a037a0a54cc8190868c1bfa1590d1a6 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:08 p.m.