Triple
T870465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-SR |
E18799
|
entity |
| Predicate | reachCategory |
P87
|
FINISHED |
| Object | short reach |
—
|
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 reach | Statement: [10GBASE-SR, reachCategory, short reach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachCategory Context triple: [10GBASE-SR, reachCategory, short reach]
-
A.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
rankingCategory
Indicates the classification or type of ranking under which an entity is evaluated or ordered.
-
C.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
D.
catchmentArea
Indicates the geographic area from which something (such as a facility, service, or natural feature) draws or collects people, resources, or water.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac94d5ac81909feee876696da589 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa89ca008190b50d061ac7fe19f9 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.