Triple

T20070484
Position Surface form Disambiguated ID Type / Status
Subject STU E499721 entity
Predicate abbreviation P43 FINISHED
Object STU 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: STU | Statement: [STU, abbreviation, STU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: STU
Context triple: [STU, abbreviation, STU]
  • A. STU chosen
    STU is a major public technical university in Bratislava, Slovakia, known for its engineering, technology, and applied science programs.
  • B. Stu
    Stu is the nickname of Stuart A. Roosa, the American astronaut who served as Command Module Pilot on the Apollo 14 mission to the Moon.
  • C. STVU
    STVU is a historically Black theological seminary at Virginia Union University known for training clergy and religious leaders in the African American Christian tradition.
  • D. STOU
    STOU is an FTP protocol command that requests the server to store a file under a unique name to avoid overwriting existing files.
  • E. ST
    ST is the common abbreviation for Sound Transit, the regional public transit agency serving the Seattle metropolitan area in Washington State.
  • 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6643798a4819081fa4e71c74b47bc completed April 20, 2026, 5:36 p.m.
Created at: April 11, 2026, 3:40 p.m.