Triple

T16721983
Position Surface form Disambiguated ID Type / Status
Subject Avaya Holdings Corp. E406369 entity
Predicate hasStockTicker P1447 FINISHED
Object AVYA E406369 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: AVYA | Statement: [Avaya Holdings Corp., hasStockTicker, AVYA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AVYA
Context triple: [Avaya Holdings Corp., hasStockTicker, AVYA]
  • A. AVYA chosen
    AVYA is the stock ticker symbol for Avaya Holdings Corp., a company that provides business communications and collaboration solutions.
  • B. AYKV
    AYKV is the ICAO airport code for Kavieng Airport in Papua New Guinea.
  • C. AV
    AV is the two-letter IATA airline designator assigned to Avianca, the flag carrier of Colombia and one of Latin America’s largest airlines.
  • D. AV
    AV is the Italian vehicle registration code assigned to the province of Avellino in the Campania region.
  • E. AVV
    AVV is the IATA airport code for Avalon Airport, a regional airport serving the Geelong and Melbourne areas in Victoria, Australia.
  • 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_69d8838f242881908abd8bc138795886 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38743750c81908a980372ad8f1a6a completed April 18, 2026, 1:29 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009d41cb6c8190bfa164ad20f009d9 completed May 10, 2026, 2:59 p.m.
Created at: April 10, 2026, 5:20 a.m.