Triple
T19709732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Communications |
E473309
|
entity |
| Predicate | telecomType |
P125698
|
FINISHED |
| Object | fixed-line operator |
—
|
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: fixed-line operator | Statement: [Mercury Communications, telecomType, fixed-line operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telecomType Context triple: [Mercury Communications, telecomType, fixed-line operator]
-
A.
telecommunicationsType
chosen
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
B.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
C.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
D.
publicTelecomOperator
Indicates that an entity functions as a telecommunications service provider that is publicly owned, controlled, or designated to operate in the public interest.
-
E.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64406f9808190acd74aa03c392eb0 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.