Triple

T29548306
Position Surface form Disambiguated ID Type / Status
Subject Polis Massa medical facility E749688 entity
Predicate in-universeTimeOfKeyEvents P45888 FINISHED
Object 19 BBY 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: 19 BBY | Statement: [Polis Massa medical facility, in-universeTimeOfKeyEvents, 19 BBY]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: in-universeTimeOfKeyEvents
Context triple: [Polis Massa medical facility, in-universeTimeOfKeyEvents, 19 BBY]
  • A. inUniverseHistory
    Indicates that an event, fact, or narrative element occurs within the fictional universe’s own internal timeline or recorded history, rather than in real-world or out-of-universe context.
  • B. fictionalUniverseEvent
    Indicates an event or occurrence that takes place within a specific fictional universe or narrative continuity.
  • C. eraChronology
    Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
  • D. chronologyIn
    Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
  • E. inUniverseDate chosen
    Indicates that an entity is associated with or occurs on a specific date within a fictional or defined universe’s internal timeline.
  • 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_69f0bd48691081908cecad39bac591e0 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66cf549788190a0084c5de634fd68 completed May 2, 2026, 9:30 p.m.
PD Predicate disambiguation batch_69f6633ac8a88190ab0cda62bbfcf9b0 completed May 2, 2026, 8:48 p.m.
Created at: April 28, 2026, 5:09 p.m.