Triple
T36839039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Legere |
E910351
|
entity |
| Predicate | implementedStrategy |
P13064
|
FINISHED |
| Object | Un-carrier initiative at T-Mobile US |
—
|
NE NERFINISHED |
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: Un-carrier initiative at T-Mobile US | Statement: [John Legere, implementedStrategy, Un-carrier initiative at T-Mobile US]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedStrategy Context triple: [John Legere, implementedStrategy, Un-carrier initiative at T-Mobile US]
-
A.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
C.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
D.
involvesStrategy
Indicates that an action, process, or situation incorporates a deliberate plan or strategy as a key component.
-
E.
laterStrategy
Indicates that one strategy or plan occurs or is implemented after another strategy in time.
- 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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.