Triple
T4260472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fast Ethernet |
E96089
|
entity |
| Predicate | distanceLimit |
P7750
|
FINISHED |
| Object | up to 2 km on 100BASE-FX multimode fiber |
—
|
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: up to 2 km on 100BASE-FX multimode fiber | Statement: [Fast Ethernet, distanceLimit, up to 2 km on 100BASE-FX multimode fiber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceLimit Context triple: [Fast Ethernet, distanceLimit, up to 2 km on 100BASE-FX multimode fiber]
-
A.
distance
chosen
Indicates the spatial separation or length between two points, objects, or locations.
-
B.
perimeterRuleDistanceLimit
Indicates a constraint that limits how far something may be from a defined perimeter or boundary.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
E.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f8103b48190934a810faafa6cb7 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.