Triple
T5362185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T U-verse |
E103046
|
entity |
| Predicate | internetServiceStatus |
P53144
|
FINISHED |
| Object | continues under AT&T brand |
—
|
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: continues under AT&T brand | Statement: [AT&T U-verse, internetServiceStatus, continues under AT&T brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internetServiceStatus Context triple: [AT&T U-verse, internetServiceStatus, continues under AT&T brand]
-
A.
serviceAvailability
Indicates whether a particular service is accessible and operational for use during a given time or under specified conditions.
-
B.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
C.
networkService
Indicates that one entity provides or participates in a network-based service or functionality for another entity or system.
-
D.
integratesISP
Indicates that one entity incorporates or connects with an Internet Service Provider (ISP) to enable or enhance network or internet-related functionality.
-
E.
typicalServiceStatus
chosen
Indicates the usual or standard operational state or condition that a service is expected to be in under normal circumstances.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.