Triple

T29492000
Position Surface form Disambiguated ID Type / Status
Subject Geonosians E748104 entity
Predicate transportSpecialty P194125 FINISHED
Object organic-looking starship designs 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: organic-looking starship designs | Statement: [Geonosians, transportSpecialty, organic-looking starship designs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: transportSpecialty
Context triple: [Geonosians, transportSpecialty, organic-looking starship designs]
  • A. transportInterface
    Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
  • B. transportFrom
    Indicates that something or someone is moved or carried away starting from a specified origin location.
  • C. transports
    Indicates that one entity carries or conveys another entity from one place to another.
  • D. publicTransit
    Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
  • E. transportFor
    Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
  • 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_69f0bd448c6881908aa6b475cefd5ddc completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fd64bc86848190a49f451a8fc5cf1e completed May 8, 2026, 4:21 a.m.
PD Predicate disambiguation batch_69fd5ff4a648819090756d90fd195d9a completed May 8, 2026, 4 a.m.
PDg Predicate description generation batch_69fd64bb345c819096a35c72784a8ce3 completed May 8, 2026, 4:21 a.m.
Created at: April 28, 2026, 4:15 p.m.