Triple

T19404831
Position Surface form Disambiguated ID Type / Status
Subject Técnico Lisboa E485425 entity
Predicate shortName P43 FINISHED
Object IST 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: IST | Statement: [Técnico Lisboa, shortName, IST]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IST
Context triple: [Técnico Lisboa, shortName, IST]
  • A. IST
    IST is the Graduate School of Information Science and Technology at the University of Tokyo, a leading institution for advanced research and education in information science, computer science, and related fields.
  • B. IST
    IST is the three-letter IATA airport code for Istanbul Airport, the main international gateway serving Istanbul, Turkey.
  • C. IST
    IST is the time zone used throughout Israel, corresponding to UTC+2 in standard time and UTC+3 during daylight saving time.
  • D. IST
    IST is the time zone used across India, corresponding to UTC+5:30 and commonly referred to as Indian Standard Time.
  • E. IST chosen
    IST is a leading Portuguese engineering and technology university known for its strong research output and rigorous academic programs.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6257a361c8190bf019fc350faa225 completed April 20, 2026, 1:09 p.m.
Created at: April 10, 2026, 1:36 p.m.