Triple
T22449902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UA |
E554962
|
entity |
| Predicate | associatedWithCompanyTickerClass |
P148239
|
FINISHED |
| Object | Class C common stock |
—
|
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: Class C common stock | Statement: [UA, associatedWithCompanyTickerClass, Class C common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCompanyTickerClass Context triple: [UA, associatedWithCompanyTickerClass, Class C common stock]
-
A.
associatedWithTicker
Indicates that an entity is linked or connected to a specific stock market ticker symbol.
-
B.
associatedCompanyTickerSuccessor
Indicates that one company ticker symbol is the successor or replacement for another company ticker symbol in an association or mapping.
-
C.
parentCompanyTicker
Indicates the stock market ticker symbol associated with the parent company of a given entity.
-
D.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
E.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
- F. None of above. chosen
Provenance (4 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ae8a08190ba6027f036ce62af |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:48 p.m.