Triple
T5167611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XDR |
E116596
|
entity |
| Predicate | hasDataRateType |
P1376
|
FINISHED |
| Object | extended data rate |
—
|
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: extended data rate | Statement: [XDR, hasDataRateType, extended data rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataRateType Context triple: [XDR, hasDataRateType, extended data rate]
-
A.
hasRateType
Indicates the specific category or scheme under which a rate (such as a price, fee, or interest) is defined or applied.
-
B.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
D.
supportsCodeRates
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
E.
hasRecordType
Indicates that an entity is associated with or classified under a specific type or category of record.
- 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_69bd445ff97c81909a2615cc56235470 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd794b87508190be3b82726ef4b37c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.