Triple
T5362186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AT&T U-verse |
E103046
|
entity |
| Predicate | phoneServiceStatus |
P31055
|
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, phoneServiceStatus, continues under AT&T brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneServiceStatus Context triple: [AT&T U-verse, phoneServiceStatus, continues under AT&T brand]
-
A.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
-
B.
hasTelephoneService
chosen
Indicates that a subject is provided with or connected to telephone service.
-
C.
callSignStatus
Indicates the current operational or regulatory state associated with an entity’s call sign, such as whether it is active, reserved, expired, or otherwise designated.
-
D.
line8Status
Indicates the status or condition associated with the eighth line in a sequence, record, or structured data set.
-
E.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
- 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.