Triple

T18099225
Position Surface form Disambiguated ID Type / Status
Subject Nostromo E433171 entity
Predicate prefix P97 FINISHED
Object USCSS 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: USCSS | Statement: [Nostromo, prefix, USCSS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: USCSS
Context triple: [Nostromo, prefix, USCSS]
  • A. USCSS chosen
    USCSS is a fictional starship registry prefix used in the Alien franchise to designate commercial spacecraft.
  • B. USSC
    USSC is an independent federal agency that develops sentencing guidelines and policies for the U.S. federal courts.
  • C. CSSC
    CSSC is a major Chinese state-owned shipbuilding conglomerate responsible for designing and constructing a wide range of commercial and military vessels.
  • D. USASC
    USASC is the commonly used abbreviation for the United States Army Signal Corps, the branch responsible for the Army’s communications and information systems.
  • E. USCM
    USCM is the commonly used abbreviation for the United States Conference of Mayors, a national organization representing the interests of cities and their mayors across the United States.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddb521448190b97d2b2aa7e4d7e6 completed April 19, 2026, 1:50 p.m.
Created at: April 10, 2026, 10:27 a.m.