Triple
T30406675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MFS Communications Company, Inc. |
E773498
|
entity |
| Predicate | hasTelecomServiceType |
P849
|
FINISHED |
| Object | local telephone service |
—
|
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: local telephone service | Statement: [MFS Communications Company, Inc., hasTelecomServiceType, local telephone service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTelecomServiceType Context triple: [MFS Communications Company, Inc., hasTelecomServiceType, local telephone service]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
hasTelephoneService
Indicates that a subject is provided with or connected to telephone service.
-
C.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
D.
hasCellService
Indicates that a location, device, or area is within range of a cellular network and can access mobile phone or data services.
-
E.
hasTelecommunicationsRole
Indicates that an entity holds or performs a specific function, position, or responsibility within the field of telecommunications.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:04 p.m.