Triple
T28613188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Data rates for GSM Evolution |
E724216
|
entity |
| Predicate | commercialDeployment |
P170668
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Enhanced Data rates for GSM Evolution, commercialDeployment, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialDeployment Context triple: [Enhanced Data rates for GSM Evolution, commercialDeployment, early 2000s]
-
A.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
B.
commercialized
Indicates that something has been developed, marketed, or exploited for profit in a commercial context.
-
C.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
D.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
E.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 28, 2026, 4:31 a.m.