Triple
T20337230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-SW |
E495645
|
entity |
| Predicate | intendedReach |
P139744
|
FINISHED |
| Object | short-range |
—
|
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: short-range | Statement: [10GBASE-SW, intendedReach, short-range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReach Context triple: [10GBASE-SW, intendedReach, short-range]
-
A.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
B.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
C.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
D.
intendedDistribution
Indicates the planned or expected way in which something is to be distributed among recipients or locations.
-
E.
availabilityTarget
Indicates that something is the intended object, resource, or condition whose availability is being specified, monitored, or constrained.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677ed75e081909bfc534033ac1c59 |
completed | April 20, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:23 a.m.