Triple
T18644613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XAUI |
E455771
|
entity |
| Predicate | aggregateRate |
P132852
|
FINISHED |
| Object | 10 Gbit/s after encoding overhead |
—
|
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: 10 Gbit/s after encoding overhead | Statement: [XAUI, aggregateRate, 10 Gbit/s after encoding overhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggregateRate Context triple: [XAUI, aggregateRate, 10 Gbit/s after encoding overhead]
-
A.
dataAggregation
Indicates the process by which multiple data points or datasets are combined into a summarized or consolidated form.
-
B.
exportRate
Indicates the rate or proportion at which goods, services, or resources are sent out from one entity or region to others.
-
C.
recordAggregateScore
Indicates recording a combined or total score derived from multiple individual scores or components.
-
D.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
E.
aggregateState
Indicates the overall or combined condition or status resulting from multiple underlying states or components.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500c36188190bfdd7aca73f3c006 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.