Triple
T15882482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boost Mobile (U.S.) |
E385105
|
entity |
| Predicate | serviceTechnology |
P120895
|
FINISHED |
| Object | 4G LTE |
—
|
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: 4G LTE | Statement: [Boost Mobile (U.S.), serviceTechnology, 4G LTE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceTechnology Context triple: [Boost Mobile (U.S.), serviceTechnology, 4G LTE]
-
A.
servicePlatform
Indicates that one entity functions as a platform or environment through which services are provided, managed, or delivered to another entity.
-
B.
technologyStack
Indicates the set of technologies, tools, and platforms used together to build or run a system, application, or project.
-
C.
serviceComponent
Indicates that one entity functions as a component or sub-part within the structure or implementation of a larger service.
-
D.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to another entity.
-
E.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
- F. None of above. chosen
Provenance (4 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
| PDg | Predicate description generation | batch_69e174da2c2c819099ec46616798245a |
completed | April 16, 2026, 11:46 p.m. |
Created at: April 10, 2026, 4:51 a.m.