Triple
T4076608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYSE:T |
E86778
|
entity |
| Predicate | issuerGICSIndustry |
P14918
|
FINISHED |
| Object | Integrated Telecommunication Services |
—
|
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: Integrated Telecommunication Services | Statement: [NYSE:T, issuerGICSIndustry, Integrated Telecommunication Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerGICSIndustry Context triple: [NYSE:T, issuerGICSIndustry, Integrated Telecommunication Services]
-
A.
industryOfUnderlyingCompany
Indicates the industry sector in which the underlying company associated with this entity operates.
-
B.
hasGICSSubIndustry
chosen
Indicates that an entity is classified within a specific GICS (Global Industry Classification Standard) sub-industry category.
-
C.
SICCode
Indicates the standardized industrial classification code that categorizes the primary type of economic activity associated with an entity or relationship.
-
D.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
E.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4ba3f08190a6c6aaf6e9c99bd5 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.