Triple
T20827039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 200 Gigabit Ethernet |
E512729
|
entity |
| Predicate | hasLowerThroughputThan |
P141976
|
FINISHED |
| Object | 400 Gigabit Ethernet |
—
|
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: 400 Gigabit Ethernet | Statement: [200 Gigabit Ethernet, hasLowerThroughputThan, 400 Gigabit Ethernet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerThroughputThan Context triple: [200 Gigabit Ethernet, hasLowerThroughputThan, 400 Gigabit Ethernet]
-
A.
slowerThan
Indicates that one entity moves or operates at a lower speed than another entity.
-
B.
hasLowerCostPerBitThan
Indicates that the cost required to transmit or store each unit of data (bit) for one entity is lower than that for another entity.
-
C.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
D.
hasLowerColumnDensityLimitThan
Indicates that the column density of one entity is constrained to be lower than the column density of another entity.
-
E.
isLessEfficientThan
Indicates that one entity performs a task or uses resources with lower efficiency compared to another entity.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fe54608190a061274bf4316610 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:42 p.m.