Triple

T23302414
Position Surface form Disambiguated ID Type / Status
Subject 3GPP2 E590337 entity
Predicate coordinatesWith P1140 FINISHED
Object TTA 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: TTA | Statement: [3GPP2, coordinatesWith, TTA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TTA
Context triple: [3GPP2, coordinatesWith, TTA]
  • A. TTA
    TTA is the IATA airport code for Raleigh Executive Jetport, a general aviation airport serving the Raleigh, North Carolina area.
  • B. TTA chosen
    TTA (Telecommunications Technology Association) is South Korea’s primary standards organization for information and communication technologies, contributing to global telecom standards development.
  • C. TAA
    TAA is the stock ticker symbol for Tandberg, a Norwegian company known for its video conferencing and telecommunication solutions.
  • D. TTE
    TTE is the stock ticker symbol for TotalEnergies SE, a major French multinational energy company involved in oil, gas, and renewable energy.
  • E. TTT
    TTT is a major Finnish theatre in Tampere known for its diverse repertoire of drama, musicals, and socially engaged productions.
  • 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_69e25d1c0ecc8190a355aa229f06d0e0 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1972406a08190bbf355cc7a9f8432 completed April 29, 2026, 5:29 a.m.
Created at: April 17, 2026, 5:04 p.m.