Triple

T5103169
Position Surface form Disambiguated ID Type / Status
Subject OFDM E115027 entity
Predicate appliedIn P1129 FINISHED
Object DAB E424819 NE 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: DAB | Statement: [OFDM, appliedIn, DAB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DAB
Context triple: [OFDM, appliedIn, DAB]
  • A. DAB
    DAB is a senior-level U.S. Department of Defense committee that reviews and approves major defense acquisition programs and policies.
  • B. DAB chosen
    DAB is the three-letter IATA airport code for Daytona Beach International Airport in Daytona Beach, Florida.
  • C. DAP
    DAP (Directory Access Protocol) is an early X.500 directory service protocol that provided a complex, OSI-based method for accessing and managing directory information before being largely replaced by LDAP.
  • D. DAP
    DAP was the abbreviation for the German Workers' Party, a far-right nationalist and anti-Semitic political party in post–World War I Germany that later evolved into the Nazi Party.
  • E. DSB
    DSB is Denmark’s national railway company, responsible for operating most passenger train services across the country.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd4440b3348190be1251fd8b7951f1 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7586a4a08190866aea6be625837c completed March 20, 2026, 4:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69beba9106ec8190839a7de183efa359 completed March 21, 2026, 3:34 p.m.
Created at: March 20, 2026, 1:41 p.m.