Triple
T10864280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alltel |
E256486
|
entity |
| Predicate | hadCustomerBase |
P33576
|
FINISHED |
| Object | millions of subscribers in the United States |
—
|
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: millions of subscribers in the United States | Statement: [Alltel, hadCustomerBase, millions of subscribers in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCustomerBase Context triple: [Alltel, hadCustomerBase, millions of subscribers in the United States]
-
A.
hasCustomers
chosen
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
B.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
-
C.
establishedBase
Indicates that an entity has set up or founded a base or primary operational location in relation to another entity or place.
-
D.
hasCustomerServices
Indicates that an entity provides or is associated with one or more customer service functions or offerings.
-
E.
initialCustomers
Indicates that the referenced entities are customers present or involved at the starting point of a process, period, or system.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516b2f148190adbacd35fc8c2056 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.