Triple

T21348111
Position Surface form Disambiguated ID Type / Status
Subject Phoenix, Arizona E526394 entity
Predicate postalAbbreviation P43 FINISHED
Object PHX
PHX is the commonly used three-letter code for Phoenix, Arizona, most notably recognized as the identifier for Phoenix Sky Harbor International Airport.
 E22401 NE FINISHED

How this triple was built (4 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: PHX | Statement: [Phoenix, Arizona, postalAbbreviation, PHX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: PHX
Context triple: [Phoenix, Arizona, postalAbbreviation, PHX]
  • A. PHX
    PHX is the three-letter FAA airport code for Phoenix Sky Harbor International Airport, the primary commercial airport serving the Phoenix, Arizona metropolitan area.
  • B. PHX
    PHX refers to the Phoenix Suns, an NBA basketball team based in Phoenix, Arizona.
  • C. Phoenix
    Phoenix is a wise and loyal elder warrior and mentor in Greek mythology, best known for guiding and advising Achilles during the Trojan War.
  • D. Phoenix
    Phoenix is a historic London theatre located on Drury Lane, known for staging a wide range of plays and musicals.
  • E. Phoenix
    Phoenix is the NATO reporting name for the AIM-54, a long-range air-to-air missile primarily used by the U.S. Navy’s F-14 Tomcat fighter aircraft.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: PHX
Triple: [Phoenix, Arizona, postalAbbreviation, PHX]
Generated description
PHX is the commonly used three-letter code for Phoenix, Arizona, most notably recognized as the identifier for Phoenix Sky Harbor International Airport.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: PHX
Target entity description: PHX is the commonly used three-letter code for Phoenix, Arizona, most notably recognized as the identifier for Phoenix Sky Harbor International Airport.
  • A. PHX chosen
    PHX is the three-letter FAA airport code for Phoenix Sky Harbor International Airport, the primary commercial airport serving the Phoenix, Arizona metropolitan area.
  • B. PHX
    PHX refers to the Phoenix Suns, an NBA basketball team based in Phoenix, Arizona.
  • C. Phoenix
    Phoenix is a small southern-sky constellation named after the mythical firebird, visible primarily from the Southern Hemisphere.
  • D. Phoenix
    Phoenix is the mascot and team name of the University of Wisconsin–Green Bay’s men’s basketball program, symbolizing resilience and renewal.
  • E. Phoenix
    Phoenix is the NATO reporting name for the AIM-54, a long-range air-to-air missile primarily used by the U.S. Navy’s F-14 Tomcat fighter aircraft.
  • F. None of above.

Provenance (5 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5baab4e081908916a289c607cf3a completed April 26, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a09a5cacbf481909ace24e0df0cd593 completed May 17, 2026, 11:26 a.m.
NEDg Description generation batch_6a09a6c435ec8190b903e953da375583 completed May 17, 2026, 11:30 a.m.
NED2 Entity disambiguation (via description) batch_6a09a7bcd5188190be3009fb3bd00af6 completed May 17, 2026, 11:34 a.m.
Created at: April 16, 2026, 5:01 p.m.