Triple

T23387494
Position Surface form Disambiguated ID Type / Status
Subject PUA-A E593923 entity
Predicate hasAbbreviation P43 FINISHED
Object PUA-A 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: PUA-A | Statement: [PUA-A, hasAbbreviation, PUA-A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PUA-A
Context triple: [PUA-A, hasAbbreviation, PUA-A]
  • A. PUA-A chosen
    PUA-A is a block of Unicode code points reserved for private, application-specific character definitions in the Supplementary Private Use Area-A range.
  • B. PUA-B
    PUA-B is a block of Unicode code points reserved for private, application-specific character definitions in the Supplementary Private Use Area-B range.
  • C. NPUA
    NPUA is a leading Armenian technical university specializing in engineering and applied sciences education and research.
  • D. PIA
    PIA is the ICAO airline designator for Pakistan International Airlines, the national flag carrier of Pakistan.
  • E. PIA
    PIA is the IATA airport code for General Wayne A. Downing Peoria International Airport, a commercial airport serving the Peoria, Illinois area.
  • 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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a498fd08819085e90a872d9d0c7a completed April 29, 2026, 6:26 a.m.
Created at: April 17, 2026, 5:35 p.m.