Triple

T37409401
Position Surface form Disambiguated ID Type / Status
Subject Twi'lek E929521 entity
Predicate galacticLanguage P188040 FINISHED
Object Galactic Basic Standard NE NERFINISHED

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: Galactic Basic Standard | Statement: [Twi'lek, galacticLanguage, Galactic Basic Standard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: galacticLanguage
Context triple: [Twi'lek, galacticLanguage, Galactic Basic Standard]
  • A. galacticDestination
    Indicates that one entity serves as the target or endpoint location within a galaxy that another entity is directed or traveling toward.
  • B. fictionalGalaxy
    Indicates that something exists within, originates from, or is associated with a galaxy that is imaginary or not part of the real universe.
  • C. galacticAffiliation
    Indicates the larger galactic group, faction, or polity with which an entity is formally associated or aligned.
  • D. inGalacticHemisphere
    Indicates that one entity is located within the same specified galactic hemisphere as another entity or reference frame.
  • E. hasGalacticContext
    Indicates that something is associated with, situated within, or characterized by a broader galactic-scale environment or framework.
  • F. None of above. chosen

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_69f76ebde49481908566cd96b37ccc84 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb9e1845e881908d19158440cf3b87 completed May 6, 2026, 8:01 p.m.
PD Predicate disambiguation batch_69fb8d08d6988190a00794ac26078348 completed May 6, 2026, 6:48 p.m.
PDg Predicate description generation batch_69fb9e173f348190b7ab5935e4dca039 completed May 6, 2026, 8:01 p.m.
Created at: May 3, 2026, 4:16 p.m.