Triple
T2998352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE5 |
E81124
|
entity |
| Predicate | impedance |
P18346
|
FINISHED |
| Object | 50 ohms |
—
|
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: 50 ohms | Statement: [10BASE5, impedance, 50 ohms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impedance Context triple: [10BASE5, impedance, 50 ohms]
-
A.
cableImpedance
chosen
Indicates the electrical opposition (impedance) presented by a cable to alternating current flow in a circuit.
-
B.
terminatorImpedance
Indicates the electrical impedance value associated with a terminator used to terminate a signal line or transmission path.
-
C.
hasOutputImpedance
Indicates that an entity (such as a device or component) exhibits a specific impedance at its output terminals.
-
D.
induction
Indicates the process by which one entity causes, initiates, or brings about a state, action, or condition in another.
-
E.
resonanceWith
Indicates a relationship where one entity aligns, harmonizes, or meaningfully connects with another in a way that amplifies or reinforces its effect or significance.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.