Triple
T9029270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCI v. AT&T |
E216127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | telecommunications law case |
C16003
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: telecommunications law case Context triple: [MCI v. AT&T, instanceOf, telecommunications law case]
-
A.
communications law
chosen
Communications law is the body of legal rules and regulations governing the transmission of information and content via electronic media, including broadcasting, telecommunications, and digital networks.
-
B.
telecommunications patent
A telecommunications patent is a legal protection granted for an invention that enables or improves the transmission, routing, or processing of information over communication networks and systems.
-
C.
telecommunications regulator
A telecommunications regulator is a governmental or independent authority responsible for overseeing, licensing, and enforcing rules in the communications sector to ensure fair competition, consumer protection, and efficient use of spectrum and infrastructure.
-
D.
telecommunications network
A telecommunications network is a system of interconnected nodes, transmission media, and protocols that enables the exchange of voice, data, and multimedia information between users and devices over distance.
-
E.
telecommunications conference
A telecommunications conference is a professional gathering where industry experts, companies, and stakeholders meet to discuss, showcase, and collaborate on current and emerging communication technologies, services, and regulations.
- F. None of above.
Provenance (1 batch)
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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:08 p.m.