Triple
T10880423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N591UA |
E256904
|
entity |
| Predicate | operatorIATA |
P12360
|
FINISHED |
| Object | UA |
E47401
|
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: UA | Statement: [N591UA, operatorIATA, UA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UA Context triple: [N591UA, operatorIATA, UA]
-
A.
UA
UA is a major public research university located in Tucson, Arizona, known for its strong programs in astronomy, space sciences, and environmental studies.
-
B.
UA
UA is the stock ticker symbol for Under Armour, Inc., an American sportswear and athletic apparel company.
-
C.
UA
UA is the commonly used abbreviation for the University of Alicante, a public university located in Alicante, Spain.
-
D.
UA
chosen
UA is the two-letter IATA airline designator used worldwide to identify United Airlines on tickets, schedules, and flight information.
-
E.
UA
UA is a common abbreviation for the University of Arkansas, a public research university known for its flagship campus in Fayetteville.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751b031a88190b1182dfc1f520264 |
completed | April 9, 2026, 7:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7e2322c8190a55605237ae6ce95 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 8, 2026, 9:21 p.m.