Triple
T28613214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enhanced Data rates for GSM Evolution |
E724216
|
entity |
| Predicate | usesMultipleTimeslots |
P173381
|
FINISHED |
| Object | for higher throughput |
—
|
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: for higher throughput | Statement: [Enhanced Data rates for GSM Evolution, usesMultipleTimeslots, for higher throughput]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMultipleTimeslots Context triple: [Enhanced Data rates for GSM Evolution, usesMultipleTimeslots, for higher throughput]
-
A.
usesMultipleVenuesIn
Indicates that an entity conducts its activities or events across more than one venue within a specified location or context.
-
B.
usesRepeatedDays
Indicates that an entity schedules, operates, or applies something on the same set of days repeatedly over time.
-
C.
isMultiDay
Indicates that the related event, activity, or condition spans more than one calendar day.
-
D.
bookingPattern
Indicates a recurring or characteristic way in which bookings are made, such as their timing, frequency, or sequence.
-
E.
availabilityPattern
Indicates a recurring schedule or pattern that defines when something is available or unavailable over time.
- 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_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 4:31 a.m.