Triple
T3398246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Alabama |
E71582
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | UA |
E71582
|
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: [University of Alabama, abbreviation, UA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UA Context triple: [University of Alabama, abbreviation, 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 two-letter IATA airline designator used worldwide to identify United Airlines on tickets, schedules, and flight information.
-
C.
UA
chosen
UA is a major public research university located in Tuscaloosa, Alabama, known for its strong academic programs and prominent Crimson Tide athletics.
-
D.
UA
UA is the two-letter ISO 3166-1 alpha-2 country code assigned to Ukraine for international standardization and identification purposes.
-
E.
UA
UA is the commonly used abbreviation for the University of Angers, a French public university located in Angers.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c5816881909f91e6e9b81d29e3 |
completed | March 8, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b34bccebdc8190bbd5f2874d06a8a7 |
completed | March 12, 2026, 11:27 p.m. |
Created at: March 8, 2026, 3:14 p.m.