Triple

T22239408
Position Surface form Disambiguated ID Type / Status
Subject DB1 E549679 entity
Predicate hasExchangeAcronym P24932 FINISHED
Object FSE 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: FSE | Statement: [DB1, hasExchangeAcronym, FSE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FSE
Context triple: [DB1, hasExchangeAcronym, FSE]
  • A. FSE
    FSE is the Faculty of Science and Engineering at the University of Groningen, encompassing a broad range of natural sciences, engineering, and technology disciplines.
  • B. FSE
    FSE (Fast Software Encryption) is a leading international research conference focused on the design and analysis of symmetric-key cryptographic primitives and algorithms.
  • C. FSE chosen
    FSE is the stock exchange abbreviation for the Frankfurt Stock Exchange in Germany.
  • D. FSE
    FSE is a premier international research conference on software engineering organized under ACM SIGSOFT.
  • E. FST
    FST is the commonly used abbreviation for the UK government ministerial post of Financial Secretary to the Treasury, a key role within HM Treasury responsible for economic and financial matters.
  • 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_69e11e4102b881909cf47d3768e25c19 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f132133b908190b0fb32a5ee68e1e6 completed April 28, 2026, 10:17 p.m.
Created at: April 16, 2026, 8:38 p.m.