Triple
T6454763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Athletic Conference |
E139963
|
entity |
| Predicate | hasAcronymUsage |
P51247
|
FINISHED |
| Object | commonly known as UAC |
—
|
LITERAL 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: commonly known as UAC | Statement: [United Athletic Conference, hasAcronymUsage, commonly known as UAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcronymUsage Context triple: [United Athletic Conference, hasAcronymUsage, commonly known as UAC]
-
A.
hasCommonAcronymUsage
Indicates that two terms share the same commonly used acronym in practice.
-
B.
usesAbbreviationIn
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
C.
isUsedInAbbreviation
chosen
Indicates that one entity functions as a shortened or abbreviated form of another entity.
-
D.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
E.
hasAcronymExpansionLanguage
Indicates that a specified language is the language in which an acronym’s full expansion is expressed.
- F. None of above.
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_69c008b301948190a35854e5284dc822 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069d339788190992e3299ffe30d58 |
completed | March 22, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:48 p.m.