Triple
T29502617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFF-8088 |
E748414
|
entity |
| Predicate | cableLengthTypical |
P18065
|
FINISHED |
| Object | up to several meters depending on data rate and cable quality |
—
|
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 several meters depending on data rate and cable quality | Statement: [SFF-8088, cableLengthTypical, up to several meters depending on data rate and cable quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableLengthTypical Context triple: [SFF-8088, cableLengthTypical, up to several meters depending on data rate and cable quality]
-
A.
cableLength
Indicates the physical length of a cable connecting or associated with an entity.
-
B.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
C.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
D.
maxCableLength
Indicates the maximum allowable length of a cable in the specified context or configuration.
-
E.
maxCableLengthDependsOn
Indicates that the maximum allowable cable length is determined or constrained by another factor, condition, or parameter.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c33d4bc81908ab72b03c1d747c6 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:25 p.m.