Triple
T3196520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSFNET |
E66947
|
entity |
| Predicate | upgradedBackboneSpeed |
P46052
|
FINISHED |
| Object | 1.5 Mbit/s |
—
|
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: 1.5 Mbit/s | Statement: [NSFNET, upgradedBackboneSpeed, 1.5 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedBackboneSpeed Context triple: [NSFNET, upgradedBackboneSpeed, 1.5 Mbit/s]
-
A.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
upgradesFrom
Indicates that one entity is a newer or improved version that replaces or enhances another entity.
-
C.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
D.
migrationSpeed
Indicates the rate at which an entity moves from one location or region to another over a given period of time.
-
E.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada7177b488190b7a1b40ff3fae15f |
completed | March 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.