Triple
T28613210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Data rates for GSM Evolution |
E724216
|
entity |
| Predicate | usesCodingSchemes |
P114887
|
FINISHED |
| Object | MCS-1 to MCS-9 |
—
|
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: MCS-1 to MCS-9 | Statement: [Enhanced Data rates for GSM Evolution, usesCodingSchemes, MCS-1 to MCS-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCodingSchemes Context triple: [Enhanced Data rates for GSM Evolution, usesCodingSchemes, MCS-1 to MCS-9]
-
A.
hasCodeScheme
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
B.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
C.
designationScheme
Indicates the classification or naming system under which an entity’s designations or identifiers are defined.
-
D.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
-
E.
usesScheme
chosen
Indicates that one entity employs, follows, or is based on a particular scheme, method, or structured plan associated with another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 4:31 a.m.