Triple
T15953613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nextel Communications |
E386876
|
entity |
| Predicate | brandPhaseOut |
P39194
|
FINISHED |
| Object | 2013 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: 2013 in the United States | Statement: [Nextel Communications, brandPhaseOut, 2013 in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandPhaseOut Context triple: [Nextel Communications, brandPhaseOut, 2013 in the United States]
-
A.
discontinuationAnnouncedBy
Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
-
B.
brandDiscontinuedAfter
Indicates that a brand ceased to exist or operate after a specified time or event.
-
C.
brandOwnerUntil
Indicates that an entity is the owner of a brand up to, but not after, a specified point in time.
-
D.
developmentPhaseAtCancellation
Indicates the specific stage of development a project or product had reached at the time it was cancelled.
-
E.
phasesOut
chosen
Indicates the process by which one entity or condition is gradually discontinued or removed in favor of another over 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.