Triple
T2108454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE-T |
E42447
|
entity |
| Predicate | minimumCableCategory |
P1373
|
FINISHED |
| Object | Cat3 UTP |
—
|
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: Cat3 UTP | Statement: [10BASE-T, minimumCableCategory, Cat3 UTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumCableCategory Context triple: [10BASE-T, minimumCableCategory, Cat3 UTP]
-
A.
cableType
chosen
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
cableImpedance
Indicates the electrical opposition (impedance) presented by a cable to alternating current flow in a circuit.
-
C.
requiresContinuousCableRun
Indicates that the relationship or action can only be fulfilled if there is an unbroken, end-to-end cable connection between the involved entities.
-
D.
circuitGrade
Indicates the quality or performance level assigned to a circuit, typically reflecting how well it meets specified standards or criteria.
-
E.
minimumCircuitsRequired
Indicates the smallest number of circuits that must be present or used for a given system, configuration, or requirement to be satisfied.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.